Skip to main content
Glama

Google keyword planner

google_keyword_planner
Read-onlyIdempotent

Reads Google's Keyword Planner for a Google Ads account. mode volumes returns how often each keyword is searched a month and its top of page bid range; mode ideas returns keywords suggested by a few words or a page (https url), most searched first, with the same figures. Counts cover the countries and language given, or everywhere. Keywords Google gives no figure for are listed apart. Gives a search campaign keywords measured on real searches. Read only.

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": {
      "input": "<input>"
    },
    "name": "google_keyword_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuine behavioral context: counts are scoped to the supplied countries/language or default to 'everywhere', ideas are returned 'most searched first', and keywords with no Google figure are segregated. It stops short of mentioning rate limits or account-permission requirements.

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 definition is front-loaded with purpose and mode behavior, and most sentences carry new information. One sentence, 'Gives a search campaign keywords measured on real searches', is vague and its referent is unclear, and 'Read only.' duplicates the readOnlyHint annotation.

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?

With no output schema, the description carries the burden of describing returns and does so reasonably: monthly search volume, top-of-page bid range, ordering for ideas, and the separate bucket for keywords without figures. It omits the concrete response shape and field naming, but an agent can call it correctly from this.

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 coverage is 75%, and the description compensates for the gaps that matter: it explains the semantics of 'mode', that the URL must be an https page (ideas-only), and that countries/language default to everywhere when omitted. The wrapper fields (accountIds, userStatement, idempotencyKey) are left to their schema descriptions, which is acceptable for generic parameters.

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 first sentence names a specific verb and resource ("Reads Google's Keyword Planner for a Google Ads account") and the next two sentences differentiate the two modes by their inputs and outputs, so the agent can tell 'volumes' from 'ideas' without opening the schema. Sibling tools like planning_calculate or brand_read_site are clearly distinct from this read-only Keyword Planner surface.

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?

It states the selecting condition for each mode: 'volumes' when you already have keywords, 'ideas' when you have only a few words or a page URL. It does not name alternative sibling tools or exclusion conditions, but the mode-selection guidance effectively answers when to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.