Grok Bot for Meta Ads: Frequency, Budgets and Leads on a Schedule

What the Bot can read in Meta

Through MCP Ads the Bot reads campaign, ad set and ad performance; daily and hourly trends; breakdowns by age and gender, placement, country and device; video completion; the funnel from impression to purchase; frequency and reach; attribution windows; delivery diagnostics; account spending limits and payment status; pixels and their event counts; and change history for a campaign, an ad set or the whole account.

It can also work across accounts: a cross-account overview returns one table for several ad accounts, and a payment check runs across several at once. For an agency Bot that is the difference between one message and ten. The wider tool set is on the Meta Ads MCP page.

Connect it in a minute

Before you paste it, open the MCP Ads dashboard, go to Connect MCP → API keys and create a key. It is shown once, so copy it then. Make one key per Bot, so you can revoke one without breaking the others. Grok Bot's sign-in flow for custom servers does not complete today, which is why the Bot uses the key header; in Grok chat or Grok Build you can instead add a custom connector at grok.com/connectors with the same URL and sign in with the browser. Then paste this into Grok Bot (connect Meta Ads in the MCP Ads dashboard first):

Connectors in Grok are account-wide, so once MCP Ads is added every Bot you make can use it. The Bot sees only the platforms and ad accounts you connected in MCP Ads, under the same workspace scope as the web app. MCP Ads has a 7-day free trial, then $49/month flat; Grok bills its own usage separately. The full setup is on the Grok Bot page and in the quickstart.

• Add a custom MCP connector:
• - Name: MCP Ads
• - URL: https://mcp-ads.com/mcp-slim
• - Header: Authorization: Bearer <paste your mcp_live_ key>
• Then list my Meta ad accounts and tell me which ad set spent the most in the last 7 days with the fewest results.

The checks worth scheduling

Frequency. Frequency is how many times, on average, each person saw your ads. When it climbs while click-through rate falls, the audience has seen the creative enough. The frequency check flags campaigns above a threshold you set (3 if you do not) and suggests refreshing the creative, reducing the budget or pausing. What threshold makes sense depends on your audience size; a small retargeting audience runs high by design.

Spend without results. Ask for ad sets that spent above a set amount in the last 7 days with no leads or purchases. That is the Meta version of Google’s wasted search terms, and it is where a daily Bot pays for itself. Budget-limited winners. The opposite problem: ad sets hitting your target cost per result but capped by budget. Meta’s delivery tends to re-learn after large budget jumps, so a Bot proposing increases in modest steps is safer than one proposing to double. Account health. A declined payment or a reached spending limit stops every campaign in the account. A payment check and the spending-limit readout are cheap to run every morning.

Prompts to give the Bot

The numbers in these prompts are illustrative. Use your own target cost per lead and spend thresholds.

• “Every morning at 7, check all my Meta ad accounts for payment errors and campaigns with frequency above 3.5. Message me only if you find something.”
• “Every day at 12, list ad sets that spent more than $50 in the last 7 days with no leads. Propose which to pause; do not pause anything until I reply.”
• “Every Monday at 8, compare last week with the week before across Meta and message me the three biggest changes in spend, results and cost per result.”
• “Which Meta ad sets are limited by budget while hitting a cost per lead under $30? How much more could each take?”
• “Export this week’s leads from all my lead forms to CSV.”
• “What changed in the account in the last 7 days, and who changed it?”
• “Break last month’s spend down by placement. Are Reels or Stories doing better on cost per result than Feed?”

What it will not do without your approval

The Bot can prepare pauses, budget changes, targeting updates, new ad sets and new ads. Every write goes through the approval and workspace controls in MCP Ads; a Bot can prepare the change, and it goes live when you approve it. New campaigns are created paused. For creative, pass images and videos as public URLs rather than asking the Bot to attach files: the upload tools fetch from a link. The Meta ad specs guide covers sizes before you ask for a new ad.

Honest limits

Meta’s reported conversions depend on the attribution window and on the pixel or Conversions API firing correctly. If a Bot tells you cost per purchase doubled, check the pixel event counts before cutting budgets. Instant-form leads are submitted inside Facebook and Instagram, so GA4 shows no conversion for them. Judge lead campaigns on Meta’s numbers and on what happens to the leads afterwards, not on site analytics. The Bot sees only ad accounts and Pages you connected in MCP Ads. If a Page or account is missing, the fix is in the Meta connection, not in Grok.