Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads generate keyword forecast metrics

google_ads_generate_keyword_forecast_metrics

Read-onlyIdempotent

Forecast impressions, clicks, CTR, CPC, cost, conversions, and CPA for temporary keyword campaigns. Supports targeting, match types, bidding strategies, and future dates without creating a live campaign.

Instructions

Forecast impressions, clicks, CTR, CPC, cost, conversions, and CPA for a temporary keyword campaign. Supports targeting, negatives, match type, three bidding strategies, explicit future dates, and an optional independent per-keyword breakdown. This read-only planless RPC does not create a campaign or saved plan.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`endDate`	No	Optional inclusive forecast end YYYY-MM-DD, no more than one year ahead; supply with startDate
`network`	No	Google Ads search network selector used for planning.	GOOGLE_SEARCH
`keywords`	Yes	Keyword phrases to analyze; use the language and market of the intended audience.
`matchType`	No	Google Ads keyword match type for the forecast.	BROAD
`maxCpcBid`	No	Bid in standard account-currency units; required for MANUAL_CPC
`startDate`	No	Optional inclusive future forecast start YYYY-MM-DD; supply with endDate
`customerId`	Yes	Google Ads serving customer ID; use a relevant client account for better estimates
`dailyBudget`	No	Daily amount in standard currency units; required for maximize strategies and optional for MANUAL_CPC
`languageIds`	No	Google Ads language constant IDs for the intended audience.
`currencyCode`	No	Optional ISO 4217 conversion currency; account currency is used by default
`geoTargetIds`	No	Google Ads geo-target constant IDs for the intended locations.
`conversionRate`	No	Expected conversion rate as a decimal, e.g. 0.02 for 2%
`biddingStrategy`	No	Supported bidding strategy for this temporary forecast. The request does not create a live campaign.	MANUAL_CPC
`maxCpcBidCeiling`	No	Optional standard-currency CPC ceiling for MAXIMIZE_CLICKS
`negativeKeywords`	No	Keyword phrases excluded from the keyword forecast.
`negativeMatchType`	No	Match type applied to the negative keywords.	BROAD
`keywordBreakdownLimit`	No	Safety cap for additional rate-limited Keyword Planner requests
`includeKeywordBreakdown`	No	Make independent one-keyword forecast calls in addition to the combined campaign forecast

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.3/5.0

Behavior4/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, and the description reinforces this with 'read-only planless RPC' and 'does not create a campaign or saved plan.' It adds the temporary-campaign context without contradicting the annotations.

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 dense sentences front-load the action and outputs, then summarize capabilities and side-effect guarantees. There is no filler or repetition of schema content.

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?

For an 18-parameter tool, the description plus a 100%-covered schema and an output schema is sufficient: the key domain caveats (temporary, planless, future dates, optional per-keyword breakdown) are present, and return values are covered by the output schema.

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 schema documents all 18 parameters. The description groups them at a high level ('targeting, negatives, match type, three bidding strategies') but adds no parameter-specific semantics beyond the schema, earning the baseline 3.

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 opening sentence names the action (Forecast), the resource (a temporary keyword campaign), and the exact metrics returned (impressions, clicks, CTR, CPC, cost, conversions, CPA). This clearly distinguishes it from siblings like google_ads_generate_keyword_historical_metrics by signaling future/temporary scope.

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 gives a clear use case—planning a temporary keyword campaign—and explicitly rules out side effects ('does not create a campaign or saved plan'). It does not name alternative tools for historical metrics or keyword ideas, so it stops short of full alternative routing.

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

Deploy Server