Skip to main content
Zoma is a set of AgentWeb tools that your own AI agent calls to work with Meta Ads. You connect it to Claude Code, Codex, or any client that supports MCP (Model Context Protocol). Your agent can then read campaign performance, upload creatives, and create or update campaigns, ad sets, and ads in your Meta ad account. Zoma runs on the same Meta connection and safety checks Emma uses. You do not need the Customer Portal or Agent Mode to use it.

What Zoma can do

Zoma does not delete campaigns, ad sets, or ads, and it does not create or upload custom audiences.

Before you begin

You need:
  • An AgentWeb account. You can create one during setup.
  • A Meta ad account you can manage. If you don’t have one yet, follow Setting up Meta Ads from scratch.
  • An agent that supports MCP, such as Claude Code or Codex. Agents without MCP can call Zoma over HTTPS.
Reads work without a payment method. Changes to ads need a payment method on file and a connected Meta ad account that granted ads management access. Adding a payment method does not charge you.

Set up Zoma

The fastest path is to ask your agent to do the setup. Your agent starts the flow, sends you links to approve, and registers the MCP server itself. You never copy a token.

Set up Zoma in your agent

1

Approve the connection

Your agent gives you a link and a short code. Open the link, sign in to AgentWeb (or sign up), and confirm the code matches.
2

Connect your Meta ad account

Your agent sends a Meta link. Sign in to Facebook, grant access, and choose the ad accounts Zoma can use.
3

Add a payment method

Your agent sends a Stripe link. Add a card. Nothing is charged. You can skip this step if you only need reads.
4

Confirm

Your agent registers the MCP server and calls zoma_status. Setup is done when it reports that everything is set.

Set up manually

If you prefer to add the server yourself, register it without a token. The first connection opens the AgentWeb login in your browser.
Then ask your agent to call zoma_status. It returns a checklist and a link for the next step. Repeat until it reports that everything is set.

Use Zoma without MCP

Agents that can’t use MCP can call the same tools over HTTPS with the bearer token from setup:

Tools

If you connected more than one ad account, your agent passes account_id to choose one.

call_meta_marketing_api actions

How changes are approved

Every change to a campaign, ad set, or ad takes two calls:
  1. Your agent sends the change without confirm. Nothing changes in Meta. Zoma returns a preview and a preview_token.
  2. Your agent shows you the preview. After you approve, it repeats the same call with confirm: true and the preview_token. The token works once and expires after 15 minutes.
If anything changed between the preview and the confirm, Zoma returns PREVIEW_MISMATCH and your agent shows you the new preview. Zoma also applies these rules:
  • New campaigns, ad sets, and ads are always created paused.
  • Turning something on is a separate change with its own preview. It can’t be combined with a budget change.
  • Creating a campaign requires an explicit objective, such as OUTCOME_LEADS or OUTCOME_SALES. Meta does not let you change it later.
  • Budgets are in major units of the ad account’s currency. 50 means $50.00 in a USD account. The preview shows the converted amount.
  • Unusually large budget changes, launches without tracking in place, and rapid repeated edits are checked or blocked, the same way they are for Emma.
  • A change is done only when the result says verification: CONFIRMED. Zoma reads the entity back from Meta to check. UNCONFIRMED or MISMATCH means the change may not have applied as intended.

Upload your own creatives

Use this when you made images or videos elsewhere, such as Higgsfield, Midjourney, Canva, or with a designer. Uploading an asset or building a creative doesn’t spend money, so these steps don’t need a preview.
1

Get the file to Zoma

If the file already has a public https URL, use that URL. If it’s on your computer, your agent calls zoma_prepare_upload with the file name and runs the returned upload command. The upload link lasts 15 minutes.
2

Upload it to your ad account

Your agent calls AD_CREATIVE UPLOAD_IMAGE (returns an image_hash) or UPLOAD_VIDEO (returns a video_id and thumbnail_url after Meta processes the video).
3

Build the creative

Your agent calls AD_CREATIVE CREATE with a name, your Page, primary text, headline, link, an optional call to action, and the image or video.
4

Create the ad

Your agent calls AD CREATE with the ad set and the new creative, using the preview and approval flow. The ad is created paused.

Example prompts

Review campaign performance

Launch ads from a folder of creatives

Usage and revoking access

Ask your agent to call zoma_usage to see this month’s tool calls and writes. To revoke a Zoma token:

Troubleshooting

Ask your agent to call zoma_status. It returns the step that is missing and a link to finish it.
Your Meta connection may have granted read-only access. Reconnect Meta through zoma_status and grant ads management.
Setup codes expire. Ask your agent to start setup again.
The change may not have applied as previewed. Ask your agent to read the entity back before retrying.
Meta is still processing the video. Your agent calls UPLOAD_VIDEO again in a minute with the video_id.

Next steps

Last modified on October 28, 2026