Introducing Assets: Bring Your Own Creative Into Your Ad Accounts From Any AI Agent
AdCrunch now lets your AI agent upload the images and video you own and register them into a Meta ad account — over the same MCP connection you already use. Meet Assets.
- Product update
- MCP
Until now, AdCrunch’s AI tools could read everything about your advertising. Your agent could pull spend, compare creative, drill into a campaign — all in plain language, all grounded in your live data.
But it couldn’t bring anything in.
Starting today, it can. Assets let your AI agent take the images and video you own, upload them to AdCrunch, and register them into an ad account’s library — so the creative is ready to use where your ads actually run. Same MCP connection. Same plain-language chat. No dashboard, no manual upload dance.
The gap between “here’s the file” and “it’s in the account”
Every performance marketer knows the tedious middle step. You have the creative — the new hero video, the seasonal image set. Before a single ad can use it, that file has to physically land in the ad platform’s media library, in the right ad account.
So you log into Ads Manager. You find the account. You upload. You wait for the video to process. Then you do it again for the next account, because a library belongs to one account, not to your whole business.
Your AI agent has been sitting right there the whole time, knowing your accounts cold — and unable to help, because it had no way to move bytes.
What’s new: Assets
An Asset is a source file you own — an image or a video — stored in AdCrunch. It belongs to your organization, not to any one ad account, and it exists before any ad references it.
Getting one in is a sentence:
Take
~/creatives/summer-launch.mp4, add it to our AdCrunch library, and register it to the Acme ad account.
Behind that sentence, your agent:
- Finds the Acme account.
- Reserves the Asset and uploads the file itself — the bytes go straight from your agent’s runtime to storage, never through the chat.
- Finalizes it into your library, checking the type and size.
- Registers it into Acme’s Meta library and reports back when it’s ready.
For video, that last step can take a few minutes while the platform processes the file — your agent just waits and tells you when it’s done.
One file, every account
Because an Asset belongs to your organization rather than a single account, you upload it once. Placing the same video in a second account skips the upload entirely — your agent just registers the Asset you already have. No re-uploading the same 200 MB file five times.
And it’s safe to ask twice. Registering the same Asset to the same account is recognized and skipped, not duplicated — so a retry never creates a mess.
Registered, not live
One important line: registering a creative makes it available, not live. The file lands in the account’s library, ready for an ad to reference. It doesn’t build an ad, change delivery, or spend a cent.
That’s deliberate. Bringing creative in is a low-stakes action, and it’s scoped that way: the permission that lets an agent upload and register (asset:write) does not let it touch budgets, pause campaigns, or change what’s running. You can hand it to a client without handing over the keys to your spend.
Meta today, more to come
Assets are live for Meta now. Support is built per-platform — every provider handles media differently — so the others follow one at a time, behind the exact same “upload and register” flow. When they land, nothing about how you ask changes.
Where it fits
Assets round out the loop your agent already runs:
- Read your accounts and performance.
- Save a playbook once and run it by name.
- Bring your own creative in — new, today.
It’s the same idea AdCrunch has had from the start: your ad stack, spoken to in plain language, from wherever your AI already lives.
Ready to hand your agent the creative?