google-ads-write-mcp

Overview Schema Source Related Servers Discussions Admin

set_status

Set a Google Ads resource to ENABLED or PAUSED using its full resource name. Dry run by default; add confirm=true to apply the status change.

Instructions

Set ENABLED or PAUSED on a campaign, ad group, ad (adGroupAds/...~~...) or keyword (adGroupCriteria/...~~...). resource_name must be the full resource name from the read MCP, e.g. customers/123/campaigns/456. Dry run unless confirm=true. (REMOVED is intentionally not supported.)

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>",
      "resource_name": "<resource_name>",
      "status": "<status>"
    },
    "name": "set_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`confirm`	No
`customer_id`	Yes
`resource_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Aug 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses a dry-run default unless confirm=true, which is critical safety-relevant behavior, and states that REMOVED is not supported. This gives the agent actionable knowledge about side effects and limitations.

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 compact sentences with no filler. The core action is front-loaded, and each sentence adds meaningful guidance: allowed values/resource types, resource_name requirement, and safety/constraint behavior.

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?

For a mutation tool with no annotations and sparse schema, the description covers the most important operational details: valid statuses, supported resource types, resource_name format, dry-run behavior, and the unsupported REMOVED state. It does not describe customer_id, but that parameter is self-explanatory. The output schema exists, so return values need not be described.

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 description coverage is 0%, so the description must compensate. It explains resource_name format with an example, enumerates valid status values, and explains the confirm parameter's dry-run semantics. customer_id is not elaborated, but it is self-evident from the name and example.

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 ('Set'), exact allowed values ('ENABLED or PAUSED'), and a clear list of target resources (campaign, ad group, ad, keyword). It also distinguishes itself from other mutation tools by focusing on status transitions and explicitly excluding REMOVED.

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?

Explains the prerequisite that resource_name must be the full resource name from the read MCP, gives an example, and clarifies that REMOVED is intentionally not supported, implying the alternative is remove_entity. It does not explicitly name sibling alternatives, but the guidance is clear enough for selection.

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