Google Ads MCP Unofficial

Overview Schema Source Related Servers Discussions Admin

Resume Keyword (gated mutation)

google_ads_resume_keyword

DestructiveIdempotent

Resume a paused Google Ads keyword by criterion ID to re-enable it for serving. Requires the customer ID, ad group ID, and explicit user intent.

Instructions

Resume (enable) a single paused keyword by criterion_id. GATED.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ad_group_id`	Yes	Ad group that owns the keyword criterion.
`customer_id`	Yes	Google Ads customer id (10 digits). Dashes optional, e.g. '1234567890' or '123-456-7890'.
`criterion_id`	Yes	Keyword criterion id (the keyword's id, NOT the keyword text).
`response_format`	No		markdown
`explicit_user_intent`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`note`	No
`error`	No
`applied`	No
`resource`	No
`reverted`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Jul 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations indicate destructiveHint=true, yet resume is a non-destructive operation; description does not clarify this discrepancy. The term 'GATED' hints at access controls but lacks detail. No further behavioral traits disclosed beyond annotations.

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

Conciseness3/5

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

Description is a single sentence, which is concise but under-specifies critical details for a gated mutation with 5 parameters. Front-loads core task but omits necessary context.

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?

As a mutation with output schema present, description should explain gating behavior, idempotency implications, and error handling. It is incomplete for effective usage, lacking details on success states, dependencies, or side effects.

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 coverage is 60% (3/5 params documented), but description adds no value beyond the schema. Key required parameter 'explicit_user_intent' has no schema description and is unmentioned in the description.

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?

Description clearly states 'Resume (enable) a single paused keyword by criterion_id', using a specific verb-resource pair. Title 'Resume Keyword (gated mutation)' and sibling context distinguish it from related tools like pause_keyword and resume_campaign.

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 mentions 'GATED' but does not explicitly explain when to use this tool over alternatives like pause_keyword or resume_campaign. No context on prerequisites or exclusions, leaving the agent to infer usage.

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

Deploy Server