Skip to main content
Glama

Keyword volume and bids (Keyword Planner)

keyword_metrics
Read-only

Fetches Google Keyword Planner search volume, competition, bid range, and monthly trends for an exact keyword list, so you can size keywords before adding them or check demand.

Instructions

Google Keyword Planner numbers for an exact list of keywords: average and monthly searches, competition and the top-of-page bid range in the account's currency. Use it to size keywords before adding them or to check a trend. Send the whole list in one call, not one per keyword: Keyword Planner rate-limits bursts. Over 100 come back as a compact table (columns, months, rows). Changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
monthsNoMonths of history to last month: 12 if left out, 48 most
keywordsYesKeywords to look up, up to 500
by_locationNoAlso count each location alone, to compare markets (up to 100 keywords)
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)
language_idNoLanguage id (1000 English, 1001 German), name or code ("de"). Leave out for the campaigns' language, or every language when you name locations
location_idsNoWhere to count searches; leave out for where the account's campaigns target. Each a geo target id (2840 United States, 2040 Austria), a country or its code ("Austria", "AT"), a place ("Springfield, Illinois"), or "worldwide" alone for every location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.46.0
    • changedInput schema / properties / location_ids / description
      Previous value: -"Where to count searches; leave out for where the account's campaigns target. Each a geo target id (2840 United States, 2040 Austria), a country or its code (\"Austria\", \"AT\"), or a place (\"Springfield, Illinois\")"New value: +"Where to count searches; leave out for where the account's campaigns target. Each a geo target id (2840 United States, 2040 Austria), a country or its code (\"Austria\", \"AT\"), a place (\"Springfield, Illinois\"), or \"worldwide\" alone for every location"
  2. Changed12 schema fields changedv0.42.0
    • addedInput schema / properties / by_location
      Added value: +{
      +  "description": "Also count each location alone, to compare markets (up to 100 keywords)",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / language_id / default
      Removed value: -"1000"
    • changedInput schema / properties / language_id / description
      Previous value: -"Google language ID. 1000 English, 1003 Spanish, 1002 French, 1001 German, 1014 Portuguese"New value: +"Language id (1000 English, 1001 German), name or code (\"de\"). Leave out for the campaigns' language, or every language when you name locations"
    • addedInput schema / properties / language_id / maxLength
      Added value: +40
    • addedInput schema / properties / language_id / minLength
      Added value: +1
    • removedInput schema / properties / language_id / pattern
      Removed value: -"^\\d+$"
    • removedInput schema / properties / location_ids / default
      Removed value: -[
      -  "2840"
      -]
    • changedInput schema / properties / location_ids / description
      Previous value: -"Google geo target IDs. 2840 United States, 2826 United Kingdom, 2124 Canada, 2036 Australia, 2356 India. For a state, city or other country, look the ID up with run_gaql: SELECT geo_target_constant.id, geo_target_constant.canonical_name FROM geo_target_constant WHERE geo_target_constant.name = 'Denver'"New value: +"Where to count searches; leave out for where the account's campaigns target. Each a geo target id (2840 United States, 2040 Austria), a country or its code (\"Austria\", \"AT\"), or a place (\"Springfield, Illinois\")"
    • addedInput schema / properties / location_ids / items / maxLength
      Added value: +80
    • addedInput schema / properties / location_ids / items / minLength
      Added value: +1
    • removedInput schema / properties / location_ids / items / pattern
      Removed value: -"^\\d+$"
    • addedInput schema / properties / months
      Added value: +{
      +  "description": "Months of history to last month: 12 if left out, 48 most",
      +  "maximum": 48,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed1 schema field changedv0.17.0
    • removedInput schema / properties / confirm_switch
      Removed value: -{
      -  "description": "Only after the user has agreed to spend their plan's account switch (a call answered \"Account switch:\"). Leave out otherwise",
      -  "type": "boolean"
      -}
  4. Changed3 schema fields changedv0.14.1
    • addedInput schema / properties / confirm_switch
      Added value: +{
      +  "description": "Only after the user has agreed to spend their plan's account switch (a call answered \"Account switch:\"). Leave out otherwise",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / keywords / description
      Previous value: -"Keywords to look up"New value: +"Keywords to look up, up to 500"
    • changedInput schema / properties / keywords / maxItems
      Previous value: -100New value: +500
  5. First observedv0.11.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and open-world, and the description reinforces this with 'Changes nothing.' It adds context the annotations don't carry: Keyword Planner rate-limits bursts, and results over 100 keywords switch to a compact table format. Both are genuine behavioral disclosures beyond structured fields.

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?

Four short sentences, front-loaded with what the tool returns, then usage, then the batching constraint, then the safety note. Every sentence carries distinct information with no redundancy.

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?

No output schema exists, yet the description names the returned metrics, the currency basis, and the alternate compact-table shape for large result sets, which is exactly what an agent needs to interpret output. Rate limits and mutation safety are also covered, leaving no material gap for a 6-parameter read tool.

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%, with every parameter individually documented in the schema, so the baseline is 3. The description contributes only marginal added meaning ('in the account's currency' and the >100 table shape) and gives no guidance on months, locations, or language tradeoffs beyond what the schema already states.

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?

States a specific verb and resource plus the exact outputs returned (average and monthly searches, competition, top-of-page bid range in account currency). The phrase 'exact list of keywords' implicitly separates it from idea-generation siblings like keyword_ideas, so an agent can route between them without opening schemas.

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?

Gives clear when-to-use guidance ('size keywords before adding them or to check a trend') and an explicit operational rule against per-keyword calls ('send the whole list in one call'). It stops short of naming an alternative tool or stating exclusions, so a 4 rather than 5.

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