Optimization on a schedule, with the leash you set.

The exception to confirm-gating, stated plainly

Everywhere else in Muze, a write previews and waits for you. Autopilot is the place where you hand over a bounded amount of that authority on purpose, because some decisions are not worth waking up for and a bid that should have moved on Tuesday is worth less on Friday.

We are not going to soften what that means. The tool that switches on Google autopilot, update_google_autopilot_settings, carries a caution in its own description saying that enabling it authorizes Muze to change budgets and bids autonomously on the daily schedule. update_amazon_autopilot_config says the same about search term and bid actions. Those warnings are in the tool metadata, which means your assistant reads them before it calls them, not just you.

Autopilot is off by default. Turning it on is a decision, and it should feel like one.

Google autopilot

Settings live behind three tools. create_google_autopilot_settings sets up defaults for the user or one customer, get_google_autopilot_settings reads back exactly what Muze is currently allowed to do, and update_google_autopilot_settings changes it, including the ability to enable campaign-level autopilot without enabling everything else.

Execution is split by level, which matters because the two operate on different things. run_google_campaign_autopilot executes Muze's stored campaign-level actions now: budget and bidding target changes. run_google_adgroup_autopilot executes ad-group-level actions: keyword and bid changes. Both are manual triggers for work that otherwise runs on the schedule, so you can run a cycle deliberately and watch what it does before trusting it to run unattended.

get_google_analysis_status is the honest one. It reports when the scheduled analysis last ran, how many campaigns were analyzed, and how many were gated out. Campaigns without enough data do not get touched, and you can see that rather than assume it.

Amazon autopilot

Amazon autopilot has two independent engines, and you can run either without the other.

run_amazon_autopilot is the search term engine. It applies eligible search term recommendations to the live account inside the configured guardrails, harvesting terms that convert and blocking the ones that spend without converting. run_amazon_bid_autopilot is the bid engine, and it changes live bids inside a fixed guardrail clip range rather than being free to move a bid anywhere it likes. get_amazon_autopilot_config reads the current configuration for a profile and update_amazon_autopilot_config changes it.

list_amazon_autopilot_actions is the audit log: every action autopilot has taken on that profile. If you only adopt one habit from this page, make it reading that log for the first fortnight after you enable anything.

Meta is not on autopilot

There are no Meta autopilot tools in the MCP inventory, and we are not going to blur that. Autopilot over MCP means Google Ads and Amazon Ads.

What Meta gets instead is a daily analysis you act on manually. get_launch_chat_thread returns the day's launch-plan analysis messages for a Meta account, get_launch_campaigns_with_ads gives the working view of active campaigns and their active ads with insights, and apply_launch_analysis_action executes the pause and scale actions inside a stored analysis message once you ask for them. Underneath that, launch_plan_pause_ads, launch_plan_enable_ads and launch_plan_scale_adsets do the individual work. It is the same analysis, with a human between the recommendation and the account.

How to turn it on without regretting it

Start read-only. Ask for get_google_autopilot_settings and get_amazon_autopilot_config so you know the current state rather than guessing at it. Then run one cycle manually with run_google_campaign_autopilot or run_amazon_autopilot, read list_amazon_autopilot_actions afterwards, and decide whether you agree with what it did.

Enable narrowly after that. Campaign-level budget changes on Google are a smaller surface than ad-group keyword changes. The Amazon search term engine is easier to reason about than the bid engine. You can revoke the whole thing by updating the config back, and access itself is revocable at the connection level.

What to type

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

• “Is autopilot on for my Google account, and what exactly is it allowed to change?”
• “Turn on campaign-level Google autopilot but leave ad group changes off.”
• “Run the Amazon search term autopilot once now, then show me the audit log.”
• “When did my scheduled Google analysis last run, and how many campaigns were gated out?”
• “Show me every autopilot action taken on this Amazon profile this month.”

The tools behind it

Reading your autopilot configuration is free of consequences. Changing it is the one setting in Muze that reduces how often you get asked.

• get_google_autopilot_settings (read): Exactly what Muze is currently allowed to change on Google.
• update_google_autopilot_settings (write): Enables autonomous budget and bid changes. Carries its own caution.
• run_google_campaign_autopilot (write): Runs stored campaign-level actions now: budgets and targets.
• run_google_adgroup_autopilot (write): Runs ad-group-level actions now: keywords and bids.
• get_google_analysis_status (read): Last scheduled run, campaigns analyzed, campaigns gated out.
• run_amazon_autopilot (write): Applies eligible search term recommendations within guardrails.
• run_amazon_bid_autopilot (write): Moves live bids inside a fixed clip range.
• list_amazon_autopilot_actions (read): The audit log of everything autopilot did.

Platforms covered. Google Ads and Amazon Ads. Meta Ads is not on autopilot over MCP.

Nothing spends without you

• Autopilot is off until you enable it. Nothing runs autonomously by default.
• The enabling tools carry an explicit caution in their own descriptions, which the assistant reads before calling them.
• Bid changes run inside a guardrail clip range rather than moving freely.
• Every action is logged and readable through list_amazon_autopilot_actions and get_google_analysis_status.
• Campaigns without enough data are gated out of analysis rather than optimized on noise.

Frequently asked questions

Does Muze change my campaigns without asking?

Only if you enable autopilot, which is off by default. Everywhere else, writes preview and wait for confirmation. Autopilot is the deliberate exception, and the tools that switch it on say so in their own descriptions.

Which platforms does autopilot cover?

Google Ads and Amazon Ads. Meta Ads has no autopilot tools over MCP. Meta instead gets a daily launch-plan analysis whose pause and scale actions you apply yourself with apply_launch_analysis_action.

What can autopilot actually change?

On Google, campaign-level budgets and bidding targets and ad-group-level keywords and bids. On Amazon, search term harvests and negatives, and bid adjustments inside a fixed clip range.

Can I see what it did?

Yes, and you should. list_amazon_autopilot_actions is a full audit log of autopilot actions on an Amazon profile, and get_google_analysis_status reports when the scheduled analysis last ran and how many campaigns it analyzed against how many it gated out.

How do I turn it off?

Update the settings back with update_google_autopilot_settings or update_amazon_autopilot_config. Beyond that, access is scoped to the accounts you authorized and can be revoked at the connection level.

Can I run it manually instead of on a schedule?

Yes, and that is the sensible way to start. run_google_campaign_autopilot, run_google_adgroup_autopilot, run_amazon_autopilot and run_amazon_bid_autopilot all execute one cycle on demand so you can inspect the result before trusting the schedule.

Read next

Other features

Or see every Muze feature.