Google Ads MCP Server

bulk_edit_operations

Execute multiple create, update, or remove operations across Google Ads resources in a single request, enabling bulk campaign changes without individual API calls.

Instructions

Perform bulk edit operations

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>",
      "operations": "<operations>"
    },
    "name": "bulk_edit_operations"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

D1.7/5.0

Behavior1/5

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

With no annotations present, the description must disclose side effects, transactional semantics, permissions, or failure behaviors. It contains none of this, leaving the agent completely uninformed about whether operations are atomic, rate-limited, or require special scopes.

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

Conciseness2/5

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

The description is under-specified rather than concise. While it is only six words, it conveys no information beyond the tool name, failing the 'every sentence earns its place' test and providing no front-loaded value.

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

Completeness1/5

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

Given the complex nested operations schema, complete absence of annotations, and no output schema, this description is vastly inadequate. It omits supported resource types, batch size limits, error handling, and output structure, making it nearly impossible to use correctly.

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 only 50%: customerId has a description but operations has none. The description adds no meaning to the complex operations array structure, leaving resourceType and operationType semantics unexplained, which is critical for correct invocation.

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

Purpose2/5

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

The description 'Perform bulk edit operations' essentially restates the tool name with a generic verb, offering no specific resource or scope. It fails to distinguish this tool from the many specific edit tools in the sibling list (e.g., update_campaign_status, create_campaign).

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?

No guidance is provided on when to use this bulk edit tool versus individual create/update/remove tools. There are no exclusions, alternatives, or contextual hints to help an agent decide when to invoke it.

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

Deploy Server