Google Ads MCP Admin

Overview Schema Source Related Servers Discussions Admin

mutations_plan_mutations

Read-only

Validate Google Ads operations and preview the outcome as an immutable plan before committing any write. Confirm every mutation without risk.

Instructions

Validate operations and return an immutable preview; makes no Ads write.

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": {
      "customer_id": "<customer_id>",
      "operations": "<operations>"
    },
    "name": "mutations_plan_mutations"
  }
}

Input Schema

Name	Required	Description	Default
`operations`	Yes
`customer_id`	Yes
`partial_failure`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context by specifying 'return an immutable preview' and reinforcing 'makes no Ads write.' This goes slightly beyond the annotations by clarifying the nature of the returned data (immutable preview) rather than just the safety profile.

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?

The description is a single sentence that is front-loaded with the verb and directly states the tool's purpose. Every word adds value, and there is no redundancy or 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?

Given the output schema and strong annotations, the description adequately conveys the tool's primary role as a non-writing validation/preview step. However, it misses details about partial_failure handling and could benefit from explicit differentiation from the many sibling mutation tools, leaving a slight gap.

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 0%, so the description must compensate. It only mentions 'operations' as the subject of validation, leaving customer_id and partial_failure completely unexplained. The description fails to provide essential parameter context.

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 clearly states the tool's function: 'Validate operations and return an immutable preview' and explicitly notes it 'makes no Ads write.' This distinguishes it from sibling tools like mutations_apply_mutation_plan, which applies plans, and mutations_get_mutation_plan, which retrieves plans.

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

Usage Guidelines3/5

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

The description implies usage for previewing/validation ('return an immutable preview'; 'makes no Ads write') but does not explicitly state when to use it over alternatives like mutations_apply_mutation_plan or mutations_get_mutation_plan. No exclusions or explicit alternative references are provided.

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

Deploy Server