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 monthly search volume, competition, and bid estimates.

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
geo_idNoGoogle Ads geo target constant ID. Defaults to '2392' (Japan). Common values: '2840' United States, '2826' United Kingdom, '2276' Germany.
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.
language_idNoGoogle Ads language constant ID. Defaults to '1005' (Japanese). Common values: '1000' English, '1002' Spanish, '1003' Korean, '1017' Chinese (Simplified).
seed_keywordsYesSeed terms used to generate ideas. 1 to 20 terms; Google Ads treats them as topic anchors, not exact match.
Behavior5/5

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

Despite no annotations, the description explicitly states 'Read-only — produces ideas but does not add anything to the account', clearly disclosing its non-destructive nature. It also lists the return fields, giving full behavioral 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?

Two concise sentences front-load purpose, return fields, safety, and sibling guidance. Every sentence is essential and 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?

Covers purpose, parameters (already well-described in schema), return fields, safety, and sibling alternative. No gaps given tool complexity and no output schema needed.

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

Parameters3/5

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

Schema coverage is 100% with detailed parameter descriptions. The tool description adds minimal extra parameter meaning beyond referencing seed_keywords. Baseline 3 is appropriate as schema already does the work.

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 it generates keyword ideas from seed terms using Google Ads API. It explicitly distinguishes from the sibling tool google_ads_keywords_add by directing the user to that tool for materialization.

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?

Explicitly states the tool is read-only and directs users to google_ads_keywords_add for adding keywords, providing clear when-to-use and when-to-use-alternative 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