← All agent use cases · Reporting use cases

A weekly read-only Meta review in Claude over Meta's own MCP that checks account changes and the purchase event before judging any ad

Reporting · Blog · · Shared by Raphael Gonzalez (Anry)

Anry founder Raphael Gonzalez published the prompt he runs every week through Meta's official Ads MCP server (mcp.facebook.com/ads). It compares the last 7 days with the 7 before and goes in a fixed order: what changed in the account and who changed it, then spend, clicks, CTR and cost per result for each active ad, which ads got worse or lost CTR day after day, delivery errors and rejections, and whether the purchase event is healthy (events received, Event Match Quality). It ends with three lines: keep, cut, and what to check on the site. Changes come first because they're quickest to rule out, and tracking comes before ads because a broken pixel makes every ad look bad. It can run as a scheduled Claude task. Because "Read only" in a prompt is only a request, the guide says to block writes with Meta's server rules in Business Suite.

ClaudeClaude CodeMeta Ads MCP

Prompt

Weekly Meta review. Ad account: <name>. Compare the last 7 days with the 7 days before.

1. What changed in the account this week, and who changed it?
2. For every active ad: spend, link clicks, CTR, cost per result, results.
3. Which ads got worse on cost per result, and which lost CTR day after day?
4. Any delivery errors, rejected ads, or anomalies Meta flags?
5. Is the purchase event healthy: events received and Event Match Quality?

Read only. Don't create, pause or edit anything.
End with three lines: keep, cut, and what to check on the site.

AdShift lists real agent workflows people have shared publicly. We summarize them and link to the original; check the source before you copy a setup.

More Reporting use cases All →

Monday brief

One new agent use case every Monday, alongside the platform changes that matter.