Agency Autopilot

Autopilot: switch on, shadow or off for a client

autopilot_set

DestructiveIdempotent

Switch Autopilot for one client: "shadow" investigates and reports what it would do, changing nothing; "on" makes the kinds of change allowed below itself (small, reversible, capped, never brand terms); "off" stops it. Shadow or on also starts a daily lead watch (needs Analytics, Search Console or Google Ads). The work runs in the agency's own Claude: "run Autopilot on X" (autopilot_start) or a weekly scheduled task (autopilot_routine gives its prompt). Budgets, bidding, new campaigns, taking pages down and messaging always come back as proposals for a person. Suggest shadow first. Premium plan.

Input Schema

Name	Required	Description
`mode`	Yes
`allow`	No	What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. Opt-in: forms, posts_more (more than one Business Profile post a week, when the agency asks for it), and reviews_low (replies to reviews under 4 stars; Autopilot asks the agency about it once). Budgets, bidding, new campaigns, taking pages down and messaging always need a person.
`client`	Yes	Client name from list_clients
`confirm`	No	Switching to shadow or on: leave false to preview what Autopilot will do; set true after the person agrees. Switching off never needs it.
`report_mode`	No	The weekly client report after each live run: ask (default: drafted, and the agency is asked to send, edit or skip), auto (send automatically, without asking; a client's first report is still asked, and one that cannot be sent is asked with the reason), off (none).
`report_language`	No	The language the client reads the weekly report in: en (default), es, pt, it, tr, id, fr or de. Autopilot writes the report's words in it, and the headings, numbers and dates follow.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

changedInput schema / properties / allow / description

Previous value: -"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. Opt-in: forms, and reviews_low (replies to reviews under 4 stars; Autopilot asks the agency about it once). Budgets, bidding, new campaigns, taking pages down and messaging always need a person."New value: +"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. Opt-in: forms, posts_more (more than one Business Profile post a week, when the agency asks for it), and reviews_low (replies to reviews under 4 stars; Autopilot asks the agency about it once). Budgets, bidding, new campaigns, taking pages down and messaging always need a person."

changedInput schema / properties / allow / items / enum

Previous value: -[
-  "ads_hygiene",
-  "ads_growth",
-  "tracking",
-  "seo",
-  "content",
-  "local",
-  "reviews_low",
-  "site_content",
-  "forms",
-  "reports",
-  "review_requests"
-]New value: +[
+  "ads_hygiene",
+  "ads_growth",
+  "tracking",
+  "seo",
+  "content",
+  "local",
+  "posts_more",
+  "reviews_low",
+  "site_content",
+  "forms",
+  "reports",
+  "review_requests"
+]

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / allow / items / enum

Previous value: -[
-  "ads_hygiene",
-  "ads_growth",
-  "tracking",
-  "seo",
-  "content",
-  "local",
-  "reviews_low",
-  "site_content",
-  "forms",
-  "reports"
-]New value: +[
+  "ads_hygiene",
+  "ads_growth",
+  "tracking",
+  "seo",
+  "content",
+  "local",
+  "reviews_low",
+  "site_content",
+  "forms",
+  "reports",
+  "review_requests"
+]

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / allow / description

Previous value: -"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. forms is opt-in. Budgets, bidding, new campaigns, taking pages down and messaging always need a person."New value: +"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. Opt-in: forms, and reviews_low (replies to reviews under 4 stars; Autopilot asks the agency about it once). Budgets, bidding, new campaigns, taking pages down and messaging always need a person."

changedInput schema / properties / allow / items / enum

Previous value: -[
-  "ads_hygiene",
-  "ads_growth",
-  "tracking",
-  "seo",
-  "content",
-  "local",
-  "site_content",
-  "forms",
-  "reports"
-]New value: +[
+  "ads_hygiene",
+  "ads_growth",
+  "tracking",
+  "seo",
+  "content",
+  "local",
+  "reviews_low",
+  "site_content",
+  "forms",
+  "reports"
+]

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / report_language

Added value: +{
+  "description": "The language the client reads the weekly report in: en (default), es, pt, it, tr, id, fr or de. Autopilot writes the report's words in it, and the headings, numbers and dates follow.",
+  "maxLength": 20,
+  "type": "string"
+}

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / report_mode / description

Previous value: -"The weekly client report after each live run: ask (default: drafted, and the agency is asked to send, edit or skip), off (none). auto (send without asking) is coming; until then it asks."New value: +"The weekly client report after each live run: ask (default: drafted, and the agency is asked to send, edit or skip), auto (send automatically, without asking; a client's first report is still asked, and one that cannot be sent is asked with the reason), off (none)."

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / report_mode

Added value: +{
+  "description": "The weekly client report after each live run: ask (default: drafted, and the agency is asked to send, edit or skip), off (none). auto (send without asking) is coming; until then it asks.",
+  "enum": [
+    "ask",
+    "auto",
+    "off"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Switching to shadow or on: leave false to preview what Autopilot will do; set true after the person agrees. Switching off never needs it.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / allow / description

Previous value: -"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new drafts only), local (a weekly Business Profile post, replies to 4-5 star reviews), reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person."New value: +"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new blog posts and pages, published live), local (a weekly Business Profile post, replies to 4-5 star reviews), site_content (text edits on live pages), reports. forms is opt-in. Budgets, bidding, new campaigns, taking pages down and messaging always need a person."

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / allow / description

Previous value: -"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person."New value: +"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, content (new drafts only), local (a weekly Business Profile post, replies to 4-5 star reviews), reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person."

changedInput schema / properties / allow / items / enum

Previous value: -[
-  "ads_hygiene",
-  "ads_growth",
-  "tracking",
-  "seo",
-  "site_content",
-  "forms",
-  "reports"
-]New value: +[
+  "ads_hygiene",
+  "ads_growth",
+  "tracking",
+  "seo",
+  "content",
+  "local",
+  "site_content",
+  "forms",
+  "reports"
+]

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / allow / description

Previous value: -"What Autopilot may change on its own when on. Default: ads_hygiene, tracking, seo, reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person."New value: +"What Autopilot may change on its own when on. Default: ads_hygiene, ads_growth (keywords from converting searches, ad assets, new ad versions, all within the existing budget), tracking, seo, reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person."

changedInput schema / properties / allow / items / enum

Previous value: -[
-  "ads_hygiene",
-  "tracking",
-  "seo",
-  "site_content",
-  "forms",
-  "reports"
-]New value: +[
+  "ads_hygiene",
+  "ads_growth",
+  "tracking",
+  "seo",
+  "site_content",
+  "forms",
+  "reports"
+]

Changed1 schema field changedOct 11, 2026

addedInput schema / properties / allow

Added value: +{
+  "description": "What Autopilot may change on its own when on. Default: ads_hygiene, tracking, seo, reports. site_content (live text edits, drafts) and forms are opt-in. Budgets, bidding, new campaigns, publishing and messaging always need a person.",
+  "items": {
+    "enum": [
+      "ads_hygiene",
+      "tracking",
+      "seo",
+      "site_content",
+      "forms",
+      "reports"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

AddedOct 10, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only carry generic hints (destructive, idempotent, open world); the description adds real substance: which change categories 'on' permits, that budgets, bidding, new campaigns, page takedowns and messaging always return as human proposals, that 'shadow' changes nothing, and that a Premium plan and a data connection are required. That is exactly the behavioral context the generic hints cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Mode semantics are front-loaded in the first sentence, and each subsequent clause carries distinct information (data requirements, execution path, human-approval boundaries, recommendation, plan gating). It is dense and parenthesis-heavy, but virtually no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, no-output-schema mutation tool, the description covers mode semantics, side effects, prerequisites, execution path and escalation boundaries. The main omission is any indication of what the call returns or what a preview looks like, though the schema's 'confirm' description partially covers the preview concept.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83% and the schema already documents 'allow', 'confirm' and 'report_mode' thoroughly, so the baseline is high. The description still adds value by explaining what 'shadow' and 'on' semantically mean for the client rather than just enumerating enum values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Switch Autopilot for one client') and immediately defines the three modes, so the agent knows exactly what the tool does and what each value means. It is clearly distinguishable from siblings like autopilot_start (which runs the work) and autopilot_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete guidance: 'Suggest shadow first', notes that shadow/on require Analytics, Search Console or Google Ads, and that the work itself runs via autopilot_start or autopilot_routine, which implicitly distinguishes this configuration tool from the execution tools. However, it does not explicitly distinguish itself from adjacent configuration siblings such as autopilot_preference or autopilot_setup_save.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agency Autopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Autopilot: switch on, shadow or off for a client

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources