Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads get search terms

google_ads_get_search_terms

Read-onlyIdempotent

Fetch Google Ads search term performance for any date range. Filter by campaign, ad group, or search term substring, and choose between search_term_view and campaign_search_term_insight reports.

Instructions

Fetch search term performance from search_term_view or campaign_search_term_insight depending on reportType.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	Yes	End date YYYY-MM-DD
`adGroupId`	No	Optional ad group ID filter. Applies directly to search_term_view and via segments.ad_group for insight reports.
`startDate`	Yes	Start date YYYY-MM-DD
`campaignId`	No	Optional campaign ID filter
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`reportType`	No	Native provider report type; determines supported metrics and dimensions.	search_term_view
`searchTermContains`	No	Optional substring filter for search_term_view

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the useful behavioral detail that the tool switches between two underlying views based on reportType, but it does not disclose pagination, return shape, or any rate-limit considerations.

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?

The description is a single, well-structured sentence that front-loads the action and conveys the only behavioral nuance that is not obvious from the schema. No filler or redundant wording.

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?

With a full output schema, complete parameter documentation, and safety annotations, the description does not need to explain return values or side effects. The only gap is the lack of use-case guidance distinguishing this tool from the similarly named paid_organic_search_terms sibling, but the required invocation context is otherwise covered.

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 already explains every parameter, including reportType's role, filters, and date formats. The description merely repeats the reportType dependency without adding deeper parameter-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Fetch search term performance') and the exact resource scope via the two report types. It is clear and distinct from general reporting tools, though it does not explicitly differentiate itself from the closely named sibling google_ads_get_paid_organic_search_terms.

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

Usage Guidelines2/5

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

The description indicates that reportType selects the source view but gives no guidance on when to choose search_term_view versus campaign_search_term_insight. It also provides no direction on when to use this tool instead of related search-term or insights tools.

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

Deploy Server