Skip to main content
Glama

google_ads_keywords_cross_adgroup_duplicates

Identifies identical keywords across ad groups in a campaign, providing performance data and a recommendation to consolidate duplicates, reducing auction competition and improving quality score.

Instructions

Finds the same text+match_type keyword appearing across multiple ad groups in a campaign. Returns groups of duplicate criteria with per-ad-group spend, conversions, and quality score, plus a consolidation recommendation (which copy to keep, which to pause/remove). Read-only. Duplicates compete in the auction and hurt aggregate quality score — run this before a keyword restructuring sprint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign to scan for duplicates.
periodNoAnalysis window used to compute per-copy spend and conversions. Accepts 'LAST_7_DAYS', 'LAST_14_DAYS', 'LAST_30_DAYS' (default), or 'YYYY-MM-DD..YYYY-MM-DD'.
Behavior4/5

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

The description explicitly states 'Read-only' and explains the behavioral impact ('Duplicates compete in the auction and hurt aggregate quality score'), adding value beyond the missing annotations. It does not disclose permissions or rate limits, but the read-only nature is sufficient.

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 concise (three sentences) and front-loaded with the core purpose. Every sentence serves a purpose: identifying duplicates, describing output, declaring read-only, and providing usage context. No unnecessary words.

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?

Given three parameters, no output schema, and the tool's complexity, the description explains return values (spend, conversions, quality score, recommendation) and use case. It could mention that campaign_id is required (though schema covers it), but overall it is complete enough for an AI agent.

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 100%, so the description does not add significant meaning beyond parameter names and types. The description mentions acceptable period values but does not elaborate on parameter semantics beyond what the schema provides.

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 clearly states the tool's purpose: finds duplicate keywords across ad groups in a campaign. It specifies the exact criteria (text+match_type) and distinguishes itself from related keyword tools by focusing on cross-adgroup duplicates.

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 provides usage context ('run this before a keyword restructuring sprint') but does not explicitly state when not to use it or list alternative tools. The message is clear enough for an AI agent to infer appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server