Skip to main content
Glama

ADS Beast

google_ads_keyword_overlap

Read-only

Finds the same keyword and match type enabled in two or more active Google campaigns of one account. Detection only.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive detection operation, so the description does not need to repeat safety claims. It adds useful behavioral scope by specifying that only active campaigns and enabled keywords are considered, though it does not describe the result shape or any limitations such as pagination or rate limits.

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 two tight sentences with the core detection scope front-loaded and no wasted wording. Every sentence contributes to defining what is detected and that the operation is detection-only.

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

Completeness3/5

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

For a simple read-only detection tool, the description adequately explains the detection target and active-campaign scope. However, it leaves the required client_id parameter completely undefined and does not describe the return value despite there being no output schema, leaving meaningful invocation gaps.

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

Parameters1/5

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

The sole required parameter, client_id, has zero schema description coverage, and the description never explains what it represents or how it should be supplied. Saying 'of one account' is only a weak implication and does not compensate for the complete lack of parameter semantics.

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 states a specific verb, 'Finds', and precisely defines the resource: the same keyword and match type enabled in two or more active Google campaigns of one account. 'Detection only' distinguishes it from remediation-oriented siblings such as prepare_google_keyword_overlap_fix without requiring the agent to open another schema.

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 gives clear usage context by scoping detection to enabled keywords, active campaigns, and a single account. 'Detection only' provides a boundary against cleanup or modification, but it does not explicitly name the alternative fix tool or state when not to use this tool.

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.