Advertising

AI agent for X Ads: campaign reports, budgets, bids and paused-first builds

TL;DR

X Ads connects through X's own sign-in (OAuth 2.0) to X's Ads MCP server and reads every ads account your X login can access. The agent reports on performance within the limits X sets, pauses and re-budgets what you approve, and builds campaigns and line items that start paused. There is no campaign delete on this API — pause is the stop — and the deletes that do exist (audiences, cards, pixels, media) wait for a person every time.

Connecting it, and what it asks for

  1. 1Open Integrations and click Connect on the X Ads card.
  2. 2Sign in to X with the account that has a role on your ads account (ads.x.com → Settings → Users), and allow access.
  3. 3Pick the ads account for the task, then write the goal.
The authorization asks for three scopes: ads.read, ads.write and offline.access (the last one is what lets the connection renew itself — without it the grant dies in two hours). Nothing about your posts, messages, likes or followers is requested. Your X login must have access to at least one ads account (create one at ads.x.com, or be added to an existing one); otherwise the connect succeeds and the account list stays empty with that reason until you Sync accounts.

What the agent reads

  • Every ads account your X login reaches, with its business, time zone, approval status and currency.
  • Funding instruments, and whether they can currently pay for delivery.
  • Campaigns (name, funding instrument, status) and line items — the ad groups that carry the objective, placements, budgets, bids, goal and dates — plus promoted posts and targeting criteria.
  • Performance by campaign, line item, promoted post or the whole account, per day, per hour or in total. X allows seven days and twenty ids per request; the agent splits a longer question and merges the answer.
  • Any other read of X's Ads MCP by name — cards, pixels (web event tags), custom audiences, the media library, posts usable as creatives, reach, placements, and the targeting searches for locations and interests.

What the agent changes — all of it approval-gated

  • Pause and activate campaigns and line items. Activation is X's own separate step, and a line item serves only once its campaign is active too.
  • Budgets — a line item's daily and total budget (on this API a campaign carries no budget of its own). The object is read first and the approval shows it before and after.
  • Bids on line items, with the bidding strategy.
  • Create campaigns and line items. Every one starts paused, whatever the request said; the budget goes on the line item.
  • Targeting — add criteria one by one (locations, interests, keywords, followers, age, gender, platform, language).
  • Everything else the server offers, by name — attach a post to a line item, write a promoted-only post, create a pixel, an audience, a card or a tracking tag.
There is no campaign or line-item delete on X's Ads MCP — pause is the stop, and a status of DELETED through any write is refused outright. The deletes that do exist (a custom audience, a card, a pixel, a media item, a tag, an app list) and removing a targeting criterion (a line item with no criteria serves broad) wait for a person on every lane: never auto-approved, never part of a batch, never on a schedule, never from an autonomous API key.

Things worth knowing before you plan around it

  • One X login can reach many ads accounts, so every call names the selected account; an id that belongs to another account is X's "not found".
  • The connection speaks X's official Ads MCP server (the transport X offers apps on its Ads Starter plan); the older REST Ads API is not used.
  • Amounts are shown in each ads account's own currency, in whole units — X's micro-units are converted at the boundary.
  • Metrics finalize with a delay, so reviews end at yesterday; days follow the ads account's time zone.
  • Budgets and bids meet an absolute ceiling, and a change far outside the current value waits for a person even under auto-approve.

Frequently asked questions

Does Agent Planners support X Ads?
Yes. Ten reads and eight approval-gated writes on X's Ads MCP cover accounts, funding, campaigns, line items, promoted posts, targeting, performance, status, line-item budgets, bids, paused creates and the server's other tools by name; the deletes that exist wait for a person every time.
Can the agent spend money on its own?
Only if you let it. By default every write waits for your approval. Under auto-approve or an autonomous API key, a budget or bid change far outside the current value — or above the absolute ceiling — is withheld for a person, and new campaigns and line items always start paused.
Can it delete campaigns?
No — X's Ads MCP has no campaign or line-item delete, so the agent pauses instead. The deletes the server does offer (audiences, cards, pixels, media, tags) are not reversible and need a person's approval every time.
Which X account should I connect with?
Any X account with a role on your ads account (ads.x.com → Settings → Users). The agent sees exactly the ads accounts that login can manage.
Connect X Ads and try it on your own account

Start free — 2,500 credits a month, no credit card. Reads are free; every write waits for you.

Related platforms

How the agent works