Skip to main content
Glama

ADS Beast

prepare_google_keyword_overlap_fix

Prepare pausing the duplicate copies of keywords that are enabled in several active Google campaigns of one account. The newest campaign keeps the keyword. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "client_id": "<client_id>",
      "reason": "<reason>"
    },
    "name": "prepare_google_keyword_overlap_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that no change occurs at prepare time, the preview_id has a 15-minute TTL, and it is single-use. It also discloses the selection rule (newest campaign keeps the keyword), which is exactly the kind of deterministic behavior an agent needs before generating a preview.

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?

Three short sentences, front-loaded with the effect, then the tie-break rule, then the safety/workflow note. Slight grammar friction in 'Prepare pausing the duplicate copies' but no filler sentences.

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 two-parameter prepare tool with no output schema, the description covers scope, selection rule, side effects, preview lifetime and the required follow-up call. Only minor gaps remain (what the preview returns, behavior on expiry, and the meaning of client_id) and none of them would cause a wrong invocation.

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

Parameters3/5

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

Schema coverage is 50%: 'reason' is documented in the schema, while 'client_id' is bare. The description's phrase 'of one account' hints that client_id identifies the Google Ads account, but it does not specify the identifier format or whether an MCC or a sub-account is expected. It adds marginal meaning beyond the schema without fully closing the gap.

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?

States a specific verb and resource: pausing duplicate keyword copies that are enabled across several active Google campaigns in one account, plus the deterministic rule that the newest campaign keeps the keyword. The intended effect is unambiguous, though it never names the sibling reporting tool (google_ads_keyword_overlap) that would naturally surface the overlaps first, so the contrast with that tool is left implicit.

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?

The description makes clear this is the first step of a two-step flow and names execute_prepared_change as the follow-up, which is the key usage context. It does not state when NOT to use it (e.g., when only one campaign has the keyword) or any prerequisites such as approval workflow or permissions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.