Skip to main content
Glama

google_ads_keywords_cross_adgroup_duplicates

Identifies duplicate keywords across ad groups in a Google Ads campaign, showing spend, conversions, and quality score per copy, and recommends which to keep or pause to improve aggregate 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
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'.
campaign_idYesCampaign to scan for duplicates.
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.
Behavior4/5

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

The description explicitly states 'Read-only', which is a key behavioral trait. It also discloses what the tool returns (groups with spend, conversions, quality score, and recommendation). No annotations are provided, so the description carries the full burden, and it does so effectively.

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 three sentences, front-loaded with the primary purpose, and every sentence adds necessary information. No redundant or extraneous 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 the tool has 3 parameters and no output schema, the description adequately covers inputs and expected outputs. It could be slightly more detailed about output structure, but it's sufficient for an analysis tool.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the default period, accepted date range format, and the customer_id fallback logic, which goes beyond the schema's descriptions.

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 it finds duplicate keywords across ad groups, returns performance data, and gives a consolidation recommendation. The tool name and description align perfectly, and it distinguishes itself from sibling keyword tools by focusing on cross-ad-group 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 advises running before a keyword restructuring sprint and explains that duplicates hurt quality score. It implies appropriate usage context, though it doesn't explicitly state when not to use or list alternatives.

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