Agent Central

Sponsored ads report

get_sponsored_ads_report

Read-only

Use for retained Sponsored Products, Sponsored Brands, and Sponsored Display report views when you need one parameterized cross-product report surface. Especially useful for SB/SD ads, search terms, targeting, purchased products, and invalid traffic that are not exposed as narrow tools. For common SP campaign/ad group/search-term workflows, the narrower SP tools may be clearer.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`asin`	No	Filter by advertised, promoted, purchased, or targeting ASIN where the selected view supports an ASIN column.
`ad_id`	No	Filter by ad/ad product-ad ID when the selected view has ad grain.
`limit`	No	Max rows (1-1000, default 20).
`offset`	No	Pagination offset (0-100000, default 0). Use the returned pagination.next_offset to continue.
`keyword`	No	Filter by keyword text (LIKE match) where the selected view includes keyword text.
`sort_by`	No	Column to sort by	spend
`end_date`	No	Optional. YYYY-MM-DD. Defaults to today if omitted.
`ad_product`	Yes	Sponsored ad product: SP (Sponsored Products), SB (Sponsored Brands), or SD (Sponsored Display).
`profile_id`	No	Filter by profile ID
`sort_order`	No	Sort order	desc
`start_date`	No	Optional. YYYY-MM-DD. Defaults to 30 days ago if omitted.
`ad_group_id`	No	Filter by ad group ID when the selected view has ad-group grain.
`campaign_id`	No	Filter by campaign ID.
`report_view`	Yes	Retained report view to query. Unsupported product/view combinations return metadata instead of guessing.
`search_term`	No	Filter by customer search term (LIKE match) for search-term views.
`target_query`	No	Filter targeting text/expression (LIKE match) for targeting views.
`ad_group_name`	No	Filter by ad group name (LIKE match) when available.
`campaign_name`	No	Filter by campaign name (LIKE match, use % for wildcards)
`non_zero_only`	No	When true, omit rows with zero or null spend, sales, orders, units, impressions, and clicks.
`include_raw_rows`	No	False returns compact rows. Default true.
`include_diagnostics`	No	True may add expanded freshness diagnostics. Basic empty-result data-window diagnostics are included by default when available.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral nuance via the schema note that unsupported product/view combinations return metadata instead of guessing. It does not discuss data freshness or rate limits, so it adds modest value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary use case and followed by the alternative routing. No wasted preamble, though the second and third sentences overlap somewhat in intent.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description adequately covers scope and routing for a 21-parameter reporting tool, leaving only minor gaps around freshness/limits.

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% with 21 well-documented parameters, so the schema carries parameter semantics. The description adds no syntax or format details beyond what the schema provides, making 3 the appropriate baseline.

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 names a specific verb and resource (retained SP/SB/SD report views) and frames the tool as a single cross-product report surface. It distinguishes itself from the many narrow sibling report tools by noting it covers SB/SD ads, search terms, targeting, purchased products, and invalid traffic. Slightly abstract ('one parameterized cross-product report surface') but an agent can place it.

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

Usage Guidelines5/5

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

It gives explicit when-to-use (retained cross-product views, especially SB/SD areas not exposed by narrow tools) and when an alternative is better ('For common SP campaign/ad group/search-term workflows, the narrower SP tools may be clearer'). This is clear routing guidance with a named alternative class.

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

All Agent Central tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.