Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_keyword_ideas

Retrieve keyword suggestions with search volume, competition, and bid estimates by entering seed keywords or a webpage URL.

Instructions

Get keyword ideas from Google Ads Keyword Planner.

Generate keyword suggestions based on seed keywords or a webpage URL. Includes search volume, competition level, and bid estimates.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) seed_keywords: Comma-separated seed keywords (e.g., "running shoes,nike") page_url: Optional URL to extract keywords from location_ids: Comma-separated location criterion IDs (default: 2840 = US) language_id: Language criterion ID (default: 1000 = English) keyword_plan_network: Network - GOOGLE_SEARCH, GOOGLE_SEARCH_AND_PARTNERS, or YOUTUBE response_format: Output format (markdown or json)

Returns: Keyword ideas with metrics (search volume, competition, bids)

Example: google_ads_keyword_ideas( customer_id="1234567890", seed_keywords="running shoes,athletic footwear", location_ids="2840", # US language_id="1000" # English )

Common Location IDs: - 2840: United States - 2826: United Kingdom - 2124: Canada - 2036: Australia

Competition Levels: - LOW: Easy to rank for - MEDIUM: Moderate competition - HIGH: Very competitive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
seed_keywordsNo
page_urlNo
location_idsNo2840
language_idNo1000
keyword_plan_networkNoGOOGLE_SEARCH
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It describes the data returned (metrics) and competition levels, but does not disclose potential API limits, data freshness, or authentication requirements. The description adds context but could be more comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for intro, args, returns, example, and common IDs. It is informative without being overly verbose. Minor improvement could be trimming redundant information, but it is well-organized.

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 the existence of an output schema (not shown), the description adequately summarizes returns. It covers parameters, examples, and common values. It could mention the response_format more explicitly, but overall it is complete for a keyword research tool.

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?

With 0% schema coverage, the description compensates fully by detailing each parameter in the 'Args' section, including defaults, examples, and explanations like location IDs and competition levels. It provides far more meaning than the bare 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's purpose: 'Get keyword ideas from Google Ads Keyword Planner.' It specifies the output includes search volume, competition level, and bid estimates. This distinguishes it from sibling tools like google_ads_keyword_forecast (forecasting) and google_ads_get_keyword_performance (historical performance).

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

Usage Guidelines4/5

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

The description explains how to generate suggestions using seed keywords or a webpage URL. It provides an example and common location/language IDs. However, it does not explicitly state when to use this tool over alternatives or mention any prerequisites like customer setup.

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/johnoconnor0/google-ads-mcp'

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