Build the campaign in a conversation. Nothing goes live until you say so.

Created paused is not a setting

The obvious objection to letting an AI build campaigns is the one we agree with: an assistant that misreads one sentence should not be able to start spending your money. So the paused state is not a default the assistant chooses. It is forced by Muze's own API before the request reaches the platform.

The tool descriptions say it in as many words. create_meta_campaign is documented as always created paused, described in the tool itself as an MCP safety rail. create_meta_campaign_flow builds all four layers and every layer is created paused. The Google launch tools force the status server side. launch_meta_ads_bulk goes further and leaves the staging ad set paused too, so a batch of forty ads cannot start spending because one of them was enabled by accident.

Enabling anything is a separate call, and those calls are classed as destructive. That is the whole design. An AI that misreads one prompt should cost you a click, not a weekend of budget.

Meta

There are two ways to build on Meta, depending on how much control you want.

The fast path is launch_meta_ad, which takes simple inputs, a title, a description, a creative URL, a landing URL, a daily budget, and assembles the campaign, ad set, creative and ad for you. Before it runs, get_meta_launch_defaults is worth a call: it reads your account's own live campaigns and recommends objective, optimization event, median budget, geo and age targeting and pixel, with a plain-English rationale for each. That matters because the alternative is an assistant inventing a budget out of nowhere. For large batches, launch_meta_ads_bulk creates many ads under a single campaign and ad set in one call, and can reuse an existing campaign or ad set instead of making new ones. Long launches can run with async_mode and be polled with get_meta_launch_status.

The precise path is the four building blocks: create_meta_campaign, create_meta_ad_set, create_meta_ad_creative and create_meta_ad, or create_meta_campaign_flow to do all four in one call. Creatives, as the tool description notes, do not spend by themselves.

Google

Seven Google campaign types have dedicated launch tools: Search, Performance Max, Shopping, Display, Demand Gen, Video and App. All of them force paused status on creation.

Google punishes launches that skip prerequisites, so Muze exposes the preflight reads as tools rather than letting the assistant guess. list_google_conversion_actions returns the conversion actions available for bidding goals. list_merchant_center_links returns the Merchant Center accounts linked to the customer, which Shopping and retail Performance Max both need, and get_merchant_feed_health reports approved and disapproved product counts before you launch against a broken feed. get_video_capabilities gates Video work, and get_app_campaign_prerequisites checks the Firebase or MMP link that an App campaign requires, because a missing link fails the launch outright.

For the campaign content itself, generate_google_keywords pulls ideas from Google's Keyword Planner, which is live platform data rather than a language model guessing at search volume, and search_geo_targets resolves cities, regions and postal codes into the geo target constants the launch payloads expect. list_google_launch_logs shows what succeeded and what failed.

Amazon

Amazon has the deepest write coverage of any platform Muze supports, 36 of its 48 tools, and campaign construction is most of the reason.

create_amazon_auto_campaign and create_amazon_manual_campaign create Sponsored Products campaigns, both paused. Underneath them, create_amazon_ad_group, create_amazon_product_ads, which creates one product ad per ASIN and per SKU, create_amazon_keywords and create_amazon_product_targets fill out the structure, and all of them are created paused as well. The exceptions are deliberate: create_amazon_negative_keywords and create_amazon_negative_product_targets are created enabled, because an exclusion that is paused excludes nothing.

There is also a guided wizard, start_amazon_campaign_wizard, which stores draft state through save_amazon_wizard_draft and transition_amazon_wizard without creating anything on Amazon, then executes the whole mutation chain through launch_amazon_wizard. Over MCP that launch is forced paused like everything else, and cancel_amazon_wizard throws the draft away without touching your account.

What it will not do

It will not turn anything on. Enabling is a separate, destructive-classed call: set_amazon_campaign_state on Amazon, resume_ad or launch_plan_enable_ads on Meta, resume_google_campaign on Google. There is no combination of prompts that ends with a live campaign you did not explicitly enable.

It also will not upload a video to Google, because Google Ads cannot: Video campaigns need YouTube video IDs that already exist.

What to type

These are prompts, not commands. Any MCP client will do: ChatGPT, Claude, Cursor or anything else that speaks the protocol.

• “Read my Meta launch defaults, then build a sales campaign for this landing page at $50 a day and leave it paused.”
• “Launch a Google Search campaign for these ten keywords, and pull keyword ideas from Planner first.”
• “Check my Merchant Center feed health, then build a Shopping campaign for the branded terms.”
• “Create a manual Sponsored Products campaign for this ASIN with these five keywords.”
• “Build twenty Meta ads from these headlines under one ad set, all paused, and show me the structure before you do.”

The tools behind it

Seven Google campaign types, two Meta launch paths plus four granular builders, and the Amazon Sponsored Products stack. All of them create paused entities.

• create_meta_campaign_flow (write): Campaign, ad set, creative and ad in one call. Every layer paused.
• launch_meta_ad (write): Meta launch from simple inputs. Always paused.
• get_meta_launch_defaults (read): Objective, budget, geo and pixel derived from your own live campaigns.
• launch_google_search (write): Search campaign, paused status forced server side.
• launch_google_pmax (write): Performance Max, same forced pause.
• generate_google_keywords (read): Keyword Planner ideas. Live platform data, no LLM.
• create_amazon_manual_campaign (write): Sponsored Products manual targeting. Created paused.
• launch_amazon_wizard (write): Executes the wizard's mutation chain, forced paused over MCP.

Platforms covered. Meta Ads, Google Ads and Amazon Ads.

Nothing spends without you

• Every campaign, ad set, ad and Amazon entity is created paused, forced server side.
• Enabling anything is a separate call classed as destructive.
• Bulk Meta launches leave the staging ad set paused too, so a batch cannot leak spend.
• Negative keywords and negative product targets are the deliberate exception: they are created enabled, because an inactive exclusion is pointless.

Frequently asked questions

Can ChatGPT create a Facebook ad campaign?

Yes, with Muze connected. launch_meta_ad builds a campaign, ad set, creative and ad from simple inputs, and create_meta_campaign_flow does the same in one structured call. Everything is created paused, so the result is a campaign waiting for your review.

Does the campaign go live immediately?

No. Every campaign Muze creates is paused, and the paused status is forced by Muze's API rather than chosen by the assistant. Turning it on is a separate action that you take.

Which Google campaign types can it launch?

Seven: Search, Performance Max, Shopping, Display, Demand Gen, Video and App. Video campaigns need existing YouTube video IDs because Google Ads cannot upload video, and App campaigns need a Firebase or MMP link, which get_app_campaign_prerequisites checks first.

Can it build Amazon Sponsored Products campaigns?

Yes, auto or manual targeting, along with ad groups, product ads for each ASIN and SKU, keywords, product targets and negatives. Everything except the exclusions is created paused.

How does it decide the budget and targeting?

It asks you, and if you want a starting point, get_meta_launch_defaults reads your account's own live campaigns and recommends an objective, optimization event, median budget and geo and age targeting, with a written rationale. Muze does not apply invented benchmarks.

What if the AI misunderstands what I asked for?

You get a paused campaign that is wrong, which you delete or fix. That is the entire argument for creating paused rather than launching and apologising afterwards.

Do I need a paid plan to launch campaigns?

Yes. Campaign creation is a write action, and the free tier is 25 read-only calls per month. Muze charges for the software and never takes a percentage of your ad spend.

Read next

Other features

Or see every Muze feature.