Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ads_generate_historical_metrics

Read-onlyIdempotent

Retrieve read-only Keyword Planner search volume, monthly volume, competition, and bid ranges for supplied keywords to analyze historical ad performance.

Instructions

Return read-only Keyword Planner search volume, monthly volume, competition, and bid ranges for supplied keywords.

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": {
      "keywords": "<keywords>"
    },
    "name": "ads_generate_historical_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYes
customer_idNo10-digit Google Ads customer ID without hyphens; defaults to configured customer.
language_idNo1000
geo_target_idsNo
year_month_rangeNoOptional {start:{year,month}, end:{year,month}} historical range.
include_average_cpcNo
keyword_plan_networkNoGOOGLE_SEARCH
include_adult_keywordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the description's "read-only" is redundant with structured data. It adds modest value by enumerating the returned metric families, but says nothing about quota/cost consumption, that results come from Google's live Keyword Planner service, or how partial keyword failures are handled.

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?

A single front-loaded sentence with no filler and the key return fields listed early. It is appropriately sized, though its brevity is partly the cause of the coverage gaps rather than pure economy.

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

Completeness2/5

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

For an 8-parameter tool with a nested year_month_range object, no output schema, and low schema coverage, the description should carry more weight. It does helpfully enumerate return values (valuable given no output schema), but leaves most parameter behavior and operational constraints unexplained.

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

Parameters2/5

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

Schema description coverage is only 25% across 8 parameters; language_id, geo_target_ids, include_average_cpc, include_adult_keywords and keyword_plan_network are undocumented in the schema, and the description compensates for none of them. It gives no meaning to geo targeting, language defaults, the year_month_range nested shape, or the 1000-keyword cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Return") plus resource (Keyword Planner search volume, monthly volume, competition, bid ranges) and the input (supplied keywords). It is distinguishable from data-retrieval siblings like ga4_run_report by its Keyword Planner scope, though it never names ads_generate_keyword_ideas as the adjacent alternative.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no prerequisites (e.g., which account or credential is needed for Keyword Planner access), and no routing to the obvious sibling ads_generate_keyword_ideas. The only usage signal is the implicit "for supplied keywords," which the schema already conveys.

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