draft_structured_snippetsCreate structured snippet assets for a Google Ads campaign and return a preview for approval.
Draft campaign structured snippet assets — returns a PREVIEW.
| Name | Required | Description | Default |
|---|---|---|---|
| snippets | Yes | ||
| campaign_id | Yes | ||
| customer_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description notes that it 'returns a PREVIEW', which clarifies the non-final nature of the operation. However, it does not specify whether any underlying draft data is persisted, and annotations are minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that efficiently conveys the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of parameter explanations and only a vague mention of a preview return, the description is insufficient for an agent to correctly construct the required input or understand the full output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has no property descriptions, and the description does not explain the structure of the 'snippets' array or the other parameters. This leaves significant ambiguity for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Draft' and the specific object 'campaign structured snippet assets', and distinguishes it from other draft tools for different asset types like callouts and sitelinks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by naming the asset type, but does not explicitly contrast with sibling tools or provide conditions for when to use it over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.