Skip to main content
Glama
Sign In
Hexagon MCP

Hexagon MCP

by smallware-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

keyword_planner_ideas

Generate keyword ideas and metrics from seed keywords: average monthly searches, competition, and top-of-page bid range using a Google Ads developer token.

Instructions

Get Keyword Planner ideas and metrics for seed keywords (read-only): average monthly searches, competition and top of page bid range. Requires a Google Ads developer token.

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>",
      "locations": "<locations>"
    },
    "name": "keyword_planner_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax ideas returned. Default 50.
networkNoDefault: google.
endMonthNoYYYY-MM.
keywordsYesSeed keywords.
locationsYesCountry codes like 'US', 'PH', or numeric geo target constant IDs.
languageIdNoLanguage constant ID. Default 1000 (English).
startMonthNoYYYY-MM. Use together with endMonth. Default: Google's last 12 months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are present, so the description must carry the full behavioral load. It does disclose that the tool is read-only and that a Google Ads developer token is required, but it does not describe quota/rate-limit behavior, failure modes, or whether the metrics are estimates or historical actuals.

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?

Two sentences with no filler. The purpose is front-loaded, with the read-only qualifier and auth prerequisite placed efficiently.

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?

The schema fully documents all seven parameters and there is no output schema, so the description's job is to cover purpose, auth, and return shape. It does those things, but leaves the agent without guidance on when to use it versus other demand/research tools.

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 description coverage is 100%, with every parameter documented in the schema. The description adds only the concept of 'seed keywords' and the returned metrics; it does not add format or constraint semantics for limit, locations, startMonth, endMonth, languageId or network.

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?

The description opens with a clear verb-resource pair ('Get Keyword Planner ideas and metrics') and enumerates the metrics returned, making the purpose more specific than the tool name alone. It does not explicitly name a sibling to distinguish from, but the Google Ads Keyword Planner resource is distinct from gsc_query, ga4_report and the reddit_* tools.

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

Usage Guidelines3/5

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

It states the input domain ('seed keywords') and a prerequisite (Google Ads developer token), but does not say when an agent should choose this tool over alternatives such as reddit_demand or gsc_query, nor does it give exclusions. Usage is implied by the resource but not explicitly routed.

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

Deploy Server

Other Tools