Skip to main content
Glama

google_ads_search_terms_analyze

Analyze keyword-search term overlap and N-gram distribution for a Google Ads campaign. Identify converting search terms to add as keywords and costly non-converting terms to exclude, with actionable insights.

Instructions

Analyze keyword/search-term overlap and N-gram distribution for a Google Ads campaign. Returns {campaign_id, period, registered_keywords_count, search_terms_count, overlap_rate (0.0-1.0), ngram_distribution:{unigrams, bigrams, trigrams} (each top-10 of {text, count, cost, conversions}), keyword_candidates:[{search_term, conversions, cost, clicks}] (CV>0 and not yet registered), negative_candidates:[{search_term, cost, clicks, impressions}] (top 20 by cost with cost>0 and conversions=0), insights:[strings]}. Read-only. For rule-scored add/exclude/watch buckets use google_ads_search_terms_review; for the raw unscored term log use google_ads_search_terms_report.

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 ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
periodNoReporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines.
Behavior5/5

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

The description explicitly declares the tool as 'Read-only,' which is a key behavioral trait. It details the full return structure, including nested objects, so the agent understands exactly what to expect.

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?

The description is thorough but somewhat lengthy due to listing the entire return structure. However, it is well-structured and front-loaded with the purpose and key differentiators. Every sentence adds value, but could be slightly more concise.

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

Completeness5/5

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

Given the tool's complexity and no output schema, the description comprehensively covers the return fields, including nested structures and their semantics. It also provides context for using the tool alongside its siblings, making it complete for an AI agent.

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 providing usage guidance for the 'period' parameter (e.g., shorter windows for recent changes, LAST_90_DAYS for trends), which goes beyond the schema's enum values.

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 analyzes keyword/search-term overlap and N-gram distribution for a Google Ads campaign. It distinguishes from siblings like google_ads_search_terms_review and google_ads_search_terms_report by specifying their different functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool vs alternatives: 'For rule-scored add/exclude/watch buckets use google_ads_search_terms_review; for the raw unscored term log use google_ads_search_terms_report.' Also mentions fallback behavior for customer_id.

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