Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ads_generate_keyword_ideas

Read-onlyIdempotent

Generate read-only Keyword Planner ideas and historical metrics from seed keywords, a page URL, or both to plan campaigns and validate demand.

Instructions

Generate read-only Keyword Planner ideas and historical metrics from seed keywords, a page URL, or both.

Input Schema

NameRequiredDescriptionDefault
urlNoOptional seed page URL.
keywordsNo
page_sizeNo
page_tokenNo
customer_idNo10-digit Google Ads customer ID without hyphens; defaults to configured customer.
language_idNoGoogle Ads language criterion ID; 1000 is English.1000
geo_target_idsNoGoogle Ads geo target criterion IDs.
keyword_plan_networkNoGOOGLE_SEARCH
include_adult_keywordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the word 'read-only' in the description is redundant. The one genuine addition is that keywords and URL may be combined ('or both'), which the schema's anyOf does not make obvious, plus the fact that results come from Google's Keyword Planner. It says nothing about quota consumption, rate limits, or result volume.

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?

A single front-loaded sentence with zero filler; the input modes are stated in the same breath as the capability.

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

Completeness3/5

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

For a 9-parameter tool with no output schema, the description covers the core intent but omits pagination semantics, default result sizing, and the shape of the returned ideas/metrics. An agent could call it, but not optimize or page it confidently 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 coverage is only 44% across 9 parameters, and the description compensates for very little. It clarifies the meaning of keywords/url but leaves page_size, page_token, keyword_plan_network, and include_adult_keywords undocumented, and says nothing about pagination behavior that page_size=1000 default implies.

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 names a specific verb ('Generate'), a specific resource ('Keyword Planner ideas and historical metrics'), and the three accepted input modes. It implicitly separates itself from ads_generate_historical_metrics by emphasizing 'ideas', but never names or contrasts that sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool for discovering keyword ideas from seeds or a URL. There is no explicit when-not guidance or routing to the closely related ads_generate_historical_metrics sibling, which is the main ambiguity here.

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