Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads get paid organic search terms

google_ads_get_paid_organic_search_terms

Read-onlyIdempotent

Retrieve paid and organic search terms from Google Ads, using combined view when available, otherwise paid-only. Filter by campaign, ad group, date range, or SERP type.

Instructions

Read-only paid/organic search terms report. Uses paid_organic_search_term_view when available and falls back to paid-only search_term_view if organic fields are unavailable.

Input Schema

TableJSON Schema

Name	Required	Description
`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
`serpType`	No	Optional search engine results page type segment filter
`adGroupId`	No	Optional ad group ID filter
`startDate`	Yes	Start date YYYY-MM-DD
`campaignId`	No	Optional campaign ID filter
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`searchTermContains`	No	Optional search term substring filter

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'Read-only' phrasing is consistent with those. It adds meaningful behavioral context by disclosing the view-selection fallback: paid_organic_search_term_view first, then paid-only search_term_view when organic fields are unavailable. This is valuable beyond 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 sentences with no filler. The core purpose is front-loaded, and the fallback behavior is stated in one additional clause. Every sentence earns its place.

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?

The tool has a full input schema, a rich set of annotations, an output schema, and a description that explains the key fallback behavior. Nothing critical is missing for an agent to select and invoke the tool correctly.

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 every parameter already has a description in the schema. The tool description adds no extra parameter-level meaning, though it does indirectly clarify the report scope. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 clearly identifies the tool as a paid/organic search terms report and defines the exact resource being read. It does not explicitly name or differentiate the sibling google_ads_get_search_terms, though the 'paid/organic' qualifier provides some implicit distinction.

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 gives no explicit guidance on when to use this tool versus alternatives such as google_ads_get_search_terms. The fallback behavior is stated, but there are no conditions, exclusions, or recommended alternative tools, leaving the agent to infer usage context.

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

Deploy Server