Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads get shopping performance

google_ads_get_shopping_performance

Read-onlyIdempotent

Retrieve Shopping performance data by product dimensions to join spend and conversions with merchant ID, item ID, title, brand, feed label, or custom labels.

Instructions

Read-only Shopping performance report keyed by Merchant Center product dimensions. Useful for joining spend/conversions to merchant ID, item ID, title, brand, feed label, and custom labels.

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	No	Optional product brand filter
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`itemId`	No	Optional Merchant Center item ID filter
`endDate`	Yes	End date YYYY-MM-DD
`adGroupId`	No	Optional ad group ID filter
`feedLabel`	No	Optional product feed label 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)
`titleContains`	No	Optional product title substring filter
`merchantCenterId`	No	Optional Merchant Center ID 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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=trueholot, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context that results are keyed by Merchant Center product dimensions, which informs how the data is organized and aggregated beyond what annotations state.

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 short sentences with no filler, and the most important information (what report and how it is keyed) appears upfront. Every phrase earns its place.

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 output schema exists and annotations cover safety, the description is sufficiently complete for a read-only reporting tool. It explains the report's purpose, key dimensions, and typical use case, though it does not mention details like date handling or pagination, which are less critical here.

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?

The input schema already has 100% coverage of parameter descriptions, so the baseline is 3. The description adds the overall context that parameters such as merchant ID, item ID, title, brand, and feed label serve as product-dimension keys for a performance report, but it does not provide detailed syntax beyond the 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 uses a specific verb and resource: 'get Shopping performance report', and clarifies it is keyed by Merchant Center product dimensions. This makes it easy to distinguish from sibling tools like google_ads_get_shopping_products or keyword performance reports.

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 explicitly states it is useful for joining spend/conversions to merchant product dimensions, giving a clear use case. It does not mention exclusions or explicitly compare to alternative tools, but the intended context is evident.

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

Deploy Server