Skip to main content
Glama
flin-google-keyword-planner-mcp

flin-google-keyword-planner-mcp

by flin-agency

keyword_ideas_from_keywords

Read-only

Generate keyword ideas from seed keywords using Google Keyword Planner data, with options for location, language, network, and metrics to support campaign planning.

Instructions

Generate keyword ideas using KeywordSeed.

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": "keyword_ideas_from_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
networkNoGOOGLE_SEARCH_AND_PARTNERS
keywordsYes
page_tokenNo
customer_idNo
language_idNo1001
location_idsNo
login_customer_idNo
keyword_annotationNo
include_average_cpcNo
aggregate_metric_typesNo
include_adult_keywordsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / language_id / default
      Previous value: -"1000"New value: +"1001"
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / include_average_cpc
      Added value: +{
      +  "default": false,
      +  "title": "Include Average Cpc",
      +  "type": "boolean"
      +}
  3. First observedv0.2.3

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no mention of upstream API quota/cost, pagination behavior despite a page_token parameter, or the MCC login-customer requirement implied by customer_id/login_customer_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is structurally clean. However, for a 12-parameter tool it is sized far too small to be useful, so brevity here reads as under-specification rather than 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?

An output schema exists, which relieves the description of explaining return values, and annotations cover the read-only profile. Still, 12 undocumented parameters, no differentiation from four close siblings, and no note of account/auth requirements leave an agent unable to configure targeting or pagination correctly from the description alone.

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 0% across 12 parameters, so the description must compensate and it does not. 'Keywords' hints at the required seed array, but limit, network, language_id, location_ids, keyword_annotation, aggregate_metric_types, include_average_cpc and include_adult_keywords are left with no meaning beyond their field names.

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

Purpose3/5

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

The verb 'Generate' plus the resource 'keyword ideas' is clear, and 'using KeywordSeed' names the underlying Google Ads idea-generation method. But it essentially restates the tool name and gives no signal distinguishing it from the four sibling keyword_ideas_* variants that differ only by seed source.

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?

There is no when-to-use guidance, no mention of prerequisites such as a Google Ads customer account, and no pointer to the URL/site/historical siblings as alternatives. The agent must infer the choice of seed type entirely from tool names.

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