Skip to main content
Glama

google_ads_search_terms_review

Score each search term in a Google Ads campaign against six hardcoded rules. Split terms into add, exclude, or watch buckets, each with a score and reason. Read-only review for campaign optimization.

Instructions

Score every search term in a Google Ads campaign against six hardcoded rules and split them into add / exclude / watch buckets. Returns {campaign_id, ad_group_id, period, target_cpa, target_cpa_source, add_candidates, exclude_candidates, watch_candidates, summary:{total_search_terms, add_count, exclude_count, watch_count}, intent_analysis?}. Each candidate has {search_term, action, match_type ('EXACT'|'PHRASE'), score (40-90), reason, metrics:{conversions, clicks, cost, ctr}}. target_cpa is resolved from the explicit argument first, then the campaign's bidding strategy, then last-30-days actual CPA; target_cpa_source reports which path ('explicit'|'bidding_strategy'|'actual'|'none'). New terms absent from the previous period are routed to watch_candidates. Read-only — emits candidates but does not add or exclude anything. Default period is LAST_7_DAYS. For keyword/N-gram overlap stats use google_ads_search_terms_analyze; for the raw query 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_7_DAYS' — this tool is tuned for short-horizon comparison. Use LAST_14_DAYS or LAST_30_DAYS for longer baselines.
target_cpaNoOptional explicit target CPA in account currency (e.g. 3000 = ¥3,000). Exclusion rule 4 fires at cost >= target_cpa * 2. Falls back to the campaign's bidding strategy target, then last-30-days actual CPA; if none can be resolved, CPA-gated rules are skipped.
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses read-only nature, target_cpa resolution logic, routing of new terms to watch_candidates, and behavior when target_cpa cannot be resolved. No contradictions.

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 well-structured and front-loaded with the main action, then details output and special behaviors. While slightly long, each sentence provides essential information.

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?

Despite no output schema, the description details the output structure comprehensively. It covers input, behavior, and use cases, but lacks explicit documentation of the 6 hardcoded rules.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining fallback logic for target_cpa and tuning for period, surpassing 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 scores search terms against six hardcoded rules and splits into add/exclude/watch buckets. It specifies the output structure and differentiates itself from sibling tools like google_ads_search_terms_analyze and google_ads_search_terms_report.

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 tells when to use this tool vs alternatives: 'For keyword/N-gram overlap stats use google_ads_search_terms_analyze; for the raw query log use google_ads_search_terms_report.' Also notes it's tuned for short-horizon comparison.

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