flin-google-keyword-planner-mcp

keyword_ideas_from_site

Read-only

Generate keyword ideas from a website URL using SiteSeed to discover relevant search terms for SEO and ad planning.

Instructions

Generate keyword ideas using SiteSeed.

Input Schema

Name	Required	Default
`limit`	No
`network`	No	GOOGLE_SEARCH_AND_PARTNERS
`site_url`	Yes
`page_token`	No
`customer_id`	No
`language_id`	No	1000
`location_ids`	No
`login_customer_id`	No
`keyword_annotation`	No
`include_average_cpc`	No
`aggregate_metric_types`	No
`include_adult_keywords`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Nov 5, 2026

addedInput schema / properties / include_average_cpc

Added value: +{
+  "default": false,
+  "title": "Include Average Cpc",
+  "type": "boolean"
+}

First observedv0.2.3May 29, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no note that this hits the Google Ads Keyword Planner API, no rate/quota implications from openWorldHint, no statement about what a "site seed" returns versus other seed types.

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?

The single sentence is short and front-loaded with the action, so it is not padded. However, brevity here comes at the cost of under-specification rather than efficiency, and the one qualifier ("SiteSeed") is jargon that conveys little.

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 so return values need not be described, but for a 12-parameter, open-world API call with an ambiguous sibling (keyword_ideas_from_url), the description is far too thin. It omits seed semantics, pagination expectations, and any differentiation from the other keyword idea tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 12 parameters with 0% schema description coverage, and the description mentions none of them. Critical fields like site_url, network, language_id, location_ids, aggregate_metric_types, keyword_annotation and page_token are left entirely unexplained in both schema and description, so an agent must guess their meaning and format.

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 description names a specific verb and resource ("Generate keyword ideas"), but qualifies it only with "using SiteSeed," an opaque term that is never explained. It does not distinguish this tool from the very similar sibling keyword_ideas_from_url, leaving an agent unable to tell which seed type applies.

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 (Google Ads auth/customer id), and no pointer to any of the sibling keyword_ideas_* alternatives. Usage must be inferred entirely from the tool name.

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

Deploy Server