Skip to main content
Glama

google_ads_keywords_suggest

Generate keyword ideas from seed terms using the Google Ads Keyword Planner API. Returns suggested keywords with average monthly searches, competition levels, and bid ranges. Use to discover advertising keywords.

Instructions

Generates new keyword ideas from seed terms using the Google Ads Keyword Planner API. Returns suggested keyword text, avg_monthly_searches, competition (LOW / MEDIUM / HIGH), top_of_page_bid_low_micros, and top_of_page_bid_high_micros. Read-only — produces ideas but does not add anything to the account. Use google_ads_keywords_add to materialize the ones you want.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
seed_keywordsYesSeed terms used to generate ideas. 1 to 20 terms; Google Ads treats them as topic anchors, not exact match.
language_idNoGoogle Ads language constant ID. Defaults to '1005' (Japanese). Common values: '1000' English, '1002' Spanish, '1003' Korean, '1017' Chinese (Simplified).
geo_idNoGoogle Ads geo target constant ID. Defaults to '2392' (Japan). Common values: '2840' United States, '2826' United Kingdom, '2276' Germany.
Behavior4/5

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

No annotations are present, so the description carries full burden. It clearly states the tool is read-only, uses the Google Ads Keyword Planner API, and does not add anything to the account. While it is transparent, additional details like rate limits or latency could further enhance it.

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 two sentences with no wasted words. It front-loads the main action and is well-structured.

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?

Although no output schema exists, the description lists all return fields (keyword text, avg_monthly_searches, competition, etc.). It covers usage, safety (read-only), and points to the sibling tool for materialization. Complete for a suggestion tool.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining that Google Ads treats seed terms as 'topic anchors, not exact match' and provides default values and common IDs for language_id and geo_id, going beyond the 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 clearly states the tool 'generates new keyword ideas from seed terms' and lists return fields. It distinguishes itself from sibling tools like google_ads_keywords_add by specifying this is read-only and does not modify the account.

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

Usage Guidelines5/5

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

The description explicitly says 'Read-only — produces ideas but does not add anything to the account.' and directs users to 'Use google_ads_keywords_add to materialize the ones you want.' This provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server