What the agent does
- Finds the campaign and reads its ad sets and settings.
- Imports your files and tracks each upload.
- Groups files into ads and ads into ad sets, the way you asked.
- Applies your naming pattern, copy, URLs and UTMs.
- Creates everything as one job and reports back in plain language.
Where it stops
An agent with access to ad spend needs limits, so these are built in:
- Nothing is created until you've seen a preview and said yes.
- New ad sets and ads are paused.
- Activating anything needs a separate, explicit yes.
- Ad set budgets above your saved cap are refused until you raise the cap.
What it doesn't do yet
Ad Uploader can report performance when you ask: spend, CTR, CPC, CPM, ROAS, purchases and leads, from the whole account down to one ad. It doesn't watch results in the background, move budgets or kill ads by itself. You decide what to change, and for catalogs, signals or A/B tests you can add Meta's own Ads MCP to the same chat.
No new dashboard to learn
The agent lives in Claude, Claude Code, Codex or Cursor. You brief it the way you'd brief a media buyer, and each ad account keeps its own saved defaults, so it asks once and remembers.
Common questions
Can the agent spend money without asking?
No. Everything it creates is paused, and activation needs your explicit yes in the conversation.
Which AI models does it work with?
Any model your MCP client supports. Ad Uploader is the connector, and your client provides the model.