Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

Google Ads: Create ad

ads_create_ad

Write a responsive search ad: 3-15 headlines (max 30 chars) and 2-4 descriptions (max 90 chars). This is the text the client's customers will read — show it to the human verbatim before confirming. Created paused.

Input Schema

NameRequiredDescriptionDefault
path1NoDisplay path after the domain, max 15 chars
path2NoSecond display path, max 15 chars
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
final_urlYesThe page this ad sends people to
headlinesYes
ad_group_idYes
customer_idYes
descriptionsYes
acknowledge_landingNoOnly after the preview's landing_check warned AND the person has seen the warnings and still wants this page. Autopilot never sets it: it proposes instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / path1 / description
      Added value: +"Display path after the domain, max 15 chars"
    • addedInput schema / properties / path2 / description
      Added value: +"Second display path, max 15 chars"
  2. Changed1 schema field changed
    • addedInput schema / properties / acknowledge_landing
      Added value: +{
+  "default": false,
+  "description": "Only after the preview's landing_check warned AND the person has seen the warnings and still wants this page. Autopilot never sets it: it proposes instead.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / confirm / default
      Added value: +false
    • addedInput schema / properties / confirm / description
      Added value: +"Leave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover safety hints (readOnlyHint false, destructiveHint false, openWorldHint true). The description adds two non-obvious traits: the ad is 'Created paused' (so it cannot go live immediately) and the text must be surfaced to the human before confirmation. It omits error/rate-limit behavior, but the key operational consequence is disclosed.

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

Conciseness5/5

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

Three tight sentences; the verb and constraints are front-loaded, the human-review requirement follows, and the paused-state fact closes with zero filler.

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?

With no output schema and 9 parameters, the description covers the content constraints, the paused creation state, and the human-approval step, which is enough to call the tool correctly. The preview/confirm mechanics live in the schema's confirm and acknowledge_landing descriptions, so the description is not obliged to repeat them.

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 56%, and the description compensates for the most important gap by adding per-item character caps (30 chars for headlines, 90 chars for descriptions) that the schema only enforces via minItems/maxItems, not maxLength. Remaining params (path1/path2, confirm, acknowledge_landing) are documented in the schema itself.

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?

States a specific verb and resource ('Write a responsive search ad'), plus concrete content constraints (3-15 headlines, 2-4 descriptions) that separate it from the sibling campaign/ad-group creation tools. An agent can identify the operation without opening the schema.

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?

Explicitly instructs showing the ad text to the human verbatim before confirming, which is real workflow guidance rather than implied usage. It does not name alternative tools (e.g. ads_add_extensions, ads_create_ad_group) or state when an agent should decline, so it falls short of full when/when-not coverage.

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

All Agency Autopilot toolsInspect
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.

Resources