Google Ads MCP Server

create_callout_assets

Create callout extensions for Google Ads by providing a customer ID and callout text.

Instructions

Create callout extensions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerId": "<customerId>",
      "callouts": "<callouts>"
    },
    "name": "create_callout_assets"
  }
}

Input Schema

Name	Required	Description	Default
`callouts`	Yes
`customerId`	Yes	Google Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the core action ('Create') but does not disclose expected effects, permission requirements, whether assets are added or replaced, or any response behavior. For a mutation tool, this is a minimal disclosure that leaves significant uncertainty.

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?

The description is a single, front-loaded phrase with no filler or repetition. It is efficient and structurally sound, but so terse that it sacrifices valuable context. Still, conciseness is about waste, and this has none, so it earns a strong score.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is far from complete. It omits any information about return values, side effects, required permissions, or relationship to other entities (only the schema implies customerId). The description offers only the most basic action, leaving the agent with insufficient context for reliable invocation.

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

Parameters2/5

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

Schema description coverage is 50% (only customerId is described). The description adds no additional parameter semantics. It mentions 'callout' which loosely maps to the 'callouts' parameter, but does not explain what calloutText should contain or how the callouts array is structured. The description fails to compensate for the documentation gap in the schema.

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

Purpose4/5

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

The description clearly states a specific verb-action ('Create') and resource ('callout extensions'), making the tool's purpose unambiguous. However, it does not distinguish this tool from the sibling tool 'create_callout_extensions', which appears to have the exact same purpose. This lack of differentiation prevents a score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It is a bare statement of action without any contextual direction. This leaves the agent to infer usage solely from the tool name and schema.

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

Deploy Server