Skip to main content
Glama

google_ads_keywords_suggest

Generate keyword ideas from seed terms using Google Ads data. Provides suggested keywords, average monthly searches, and competition levels.

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?

Discloses key behavioral trait: read-only, no account modification. Since no annotations are provided, the description carries full burden; it could add details like rate limits or pagination, but the read-only stance is clear.

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?

Three sentences, each essential: core purpose, read-only nature, and next-step sibling reference. No unnecessary words; front-loaded with action and output info.

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

Completeness4/5

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

Given 4 parameters and no output schema, the description covers purpose, output fields, read-only nature, and related tool. Could mention limit on returned ideas or error conditions, but sufficient 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 coverage is 100%, but description adds value: explains seed_keywords are treated as topic anchors, provides common language/geo IDs, and clarifies default values. This goes beyond schema descriptions.

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 the Google Ads Keyword Planner API, listing specific return fields. It distinguishes itself from siblings like google_ads_keywords_add by noting it is read-only and produces ideas without adding to 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?

Explicitly tells when to use this tool (for idea generation) and when not to (not for materializing ideas), and directly names the alternative tool (google_ads_keywords_add) for the next step.

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