Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads generate keyword ideas

google_ads_generate_keyword_ideas

Read-onlyIdempotent

Generate keyword ideas from seeds, a URL, or a whole site, returning historical volume, trends, competition, and bids for Google Ads planning.

Instructions

Discover Keyword Planner ideas from up to 20 seed keywords, a URL, keywords plus URL, or a whole site. Returns historical volume, monthly trends, computed 3-month/YoY changes, competition, bids, close variants, optional concepts, and pagination. Read-only; no plan is saved.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	Specific page URL to crawl; combine with seedKeywords if desired
`site`	No	Whole-domain seed; exclusive with seedKeywords/url
`network`	No	Google Ads search network selector used for planning.	GOOGLE_SEARCH
`pageSize`	No	Google supports up to 10,000; keep pages small for interactive MCP use and use larger pages only for controlled exports
`pageToken`	No	nextPageToken from a prior identical request
`customerId`	Yes	Google Ads serving customer ID; use the client account, not its MCC manager
`languageId`	No	Google Ads language constant ID for the keyword request.
`endYearMonth`	No	Last year and month of the historical metrics period.
`geoTargetIds`	No	Google Ads geo-target constant IDs for the intended locations.
`seedKeywords`	No	Seed keyword phrases from which Google generates keyword ideas.
`historyMonths`	No	13 months is enough to compute latest-month YoY while limiting response size
`startYearMonth`	No	First year and month of the historical metrics period.
`includeAverageCpc`	No	Request average cost-per-click metrics when available.
`includeAdultKeywords`	No	Allow adult keyword ideas where supported by the provider and the selected market.
`includeDeviceBreakdown`	No	Include device-specific planning metrics when supported.
`includeKeywordConcepts`	No	Include Google's keyword concept grouping metadata.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, so the bar is lower. The description adds value beyond those hints by disclosing 'no plan is saved' and by enumerating what the call returns: historical volume, monthly trends, computed 3-month/YoY changes, competition, bids, close variants, optional concepts, and pagination.

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, front-loaded with the core ideation purpose, followed by output highlights and the read-only/no-save caveat. Every sentence earns its place, and there is no repetition of schema boilerplate or filler.

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 16-parameter schema with 100% coverage, rich annotations, and an output schema, the description is largely complete: it states the operation, accepted input sources, key returned metrics, and mutation safety. The main missing piece is explicit sibling routing, but that is already captured under usage guidelines and does not make the description inadequate overall.

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 description coverage is 100%, so the baseline is 3 even without extra parameter explanation. The description adds some contextual meaning, such as the combination of 'keywords plus URL' and the exclusivity implied by 'a whole site,' but it does not materially clarify the many other parameters beyond what the schema already documents.

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 uses a specific verb-resource pair ('Discover Keyword Planner ideas') and enumerates the input modes: seed keywords, URL, keywords plus URL, or a whole site. It clearly differentiates this ideation tool from sibling read-only retrieval tools like google_ads_get_keyword_performance and even from its nearest relatives, google_ads_generate_keyword_historical_metrics and google_ads_generate_keyword_forecast_metrics.

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 input modes ('from up to 20 seed keywords, a URL, keywords plus URL, or a whole site') imply when to use the tool, but there is no explicit statement about when to choose this over the sibling keyword metrics/forecast generators. No alternatives or exclusion conditions are named, so the guidance is implied rather than explicit.

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

Deploy Server