google-ads-mcp

by scalably-io

Overview Schema Source Related Servers Score Discussions Admin

Python

Remote

google_ads_keyword_ideas

Read-only

Generate keyword ideas with search volume, competition, and CPC estimates from seed keywords or a page URL.

Instructions

Generate keyword ideas with search volume + competition + CPC estimates.

Args: customer_id: customer_id to attribute the request (any Ads account under MCC works). keywords: seed keywords, list of strings. Optional if page_url is given. page_url: seed URL (crawled for keyword extraction). Optional if keywords given. language_id: Google language criterion ID. Default '1000' (English). Common: '1001' Spanish, '1002' French, '1003' German, '1007' Italian. geo_target_ids: list of geo criterion IDs. Default ['2840'] (US). Common: '2826' UK, '2124' Canada, '2036' Australia, '2276' Germany. keyword_network: GOOGLE_SEARCH (default) | GOOGLE_SEARCH_AND_PARTNERS. include_adult: include adult-category keywords (default False). page_size: max ideas to return (default 100, capped at 10000).

Returns: {ideas: [{text, avg_monthly_searches, competition, low_top_of_page_bid_micros, high_top_of_page_bid_micros, concept_group}]}.

Rate limit: 1 QPS for this service. Back off on RESOURCE_EXHAUSTED. Requires Basic Access (Explorer may 403); if you get USER_PERMISSION_DENIED, the dev_token tier is too low.

Input Schema

TableJSON Schema

Name	Required	Default
`keywords`	No
`page_url`	No
`page_size`	No
`customer_id`	Yes
`language_id`	No	1000
`include_adult`	No
`geo_target_ids`	No
`keyword_network`	No	GOOGLE_SEARCH

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavioral details: the 1 QPS rate limit, RESOURCE_EXHAUSTED backoff guidance, Basic Access requirement, possible 403 for Explorer, and dev_token tier issues. It also clarifies defaults and the max page_size cap, adding substantial operational context.

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?

The description is appropriately sized for a tool with 8 parameters and multiple behavioral caveats. It front-loads the purpose, then organizes Args and Returns in a compact, scannable format. No sentence is wasted.

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

Completeness5/5

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

The description covers input semantics, defaults, output shape, rate limiting, authentication requirements, and error hints. With an output schema already present, the return-format inclusion is a bonus. There are no obvious gaps for an agent to invoke the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by explaining every parameter: customer_id attribution, seed keywords, page_url optionality, language_id and geo_target_ids with common IDs, keyword_network values, include_adult default, and page_size cap. This goes far beyond the raw schema.

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 description opens with a specific verb and resource: 'Generate keyword ideas with search volume + competition + CPC estimates.' This clearly distinguishes the tool from siblings like historical or forecast metrics, even without naming them. The tool's purpose is unambiguous.

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?

The description provides clear guidance on parameter alternatives, such as keywords vs page_url and language/geo defaults, but it does not explicitly state when to choose this tool over siblings like keyword_historical_metrics or keyword_forecast_metrics. Usage context is implied by the 'ideas' focus rather than stated with exclusions.

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

Install Server