Gloriads — Amazon Ads

Streaming TV figures

get_streaming_tv_report

Read-onlyIdempotent

Get the Streaming TV (TV ads: Prime Video, streaming apps) campaigns of ONE marketplace over a period of at most 31 days within the last 95 days: spend, impressions, CPM, clicks, sales, purchases and units, per campaign and in total, in the marketplace's own currency (not USD). The other reports leave Streaming TV out. If status is "pending", Amazon is making the report: call again after meta.retry_after_seconds. "unavailable": Amazon does not offer Streaming TV to this account (KDP authors).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "marketplace_id": "<marketplace_id>"
    },
    "name": "get_streaming_tv_report"
  }
}

Input Schema

Name	Required	Description
`range`	No	Relative period, resolved in `timezone`, e.g. "last_30_days", "this_month", "last_year", or "all_time" (from the oldest data held, through today). Ranges cover complete days like the dashboard: "last_30_days" is the 30 days ending yesterday, "this_month" stops at yesterday, "today" is today. Defaults to "last_30_days". Do not combine with start_date/end_date.
`end_date`	No	Last day, inclusive (YYYY-MM-DD). A date after today is treated as today.
`timezone`	No	IANA time zone deciding which day "today" is for `range`, e.g. "Europe/Paris". Defaults to UTC.
`start_date`	No	First day, inclusive (YYYY-MM-DD). Send together with end_date.
`marketplace_id`	Yes	The marketplace: an `id` from list_marketplaces.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds genuinely new behavioral context: asynchronous report generation signaled by status "pending" with a retry interval, an availability failure mode tied to account type, and the fact that results are returned per campaign and in total using local currency rather than USD. These are operational details the agent cannot infer from 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.

Conciseness4/5

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

Front-loaded with the resource, metrics and scope limits, then the sibling exclusion, then the status-code handling — a sensible priority order with no filler. It is a single dense, slightly run-on block, but every clause carries information.

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?

For a read-only report tool with no output schema, the description usefully enumerates the returned metrics and their granularity (per campaign and in total) alongside currency semantics and failure handling. The one gap is the unresolved tension between the described 31-day/95-day window and the broader range enum, which an agent would need to resolve by trial.

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 coverage is 100%, so range, dates, timezone and marketplace_id are already documented in detail, and the description correctly reinforces that marketplace_id scopes to a single marketplace from list_marketplaces. However, the stated window ("at most 31 days within the last 95 days") conflicts with enum values the schema permits, such as last_90_days, last_year and all_time, leaving the agent unsure which constraint governs rather than clarifying parameter use.

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?

States a specific verb and resource (get Streaming TV campaign figures: spend, impressions, CPM, clicks, sales, purchases, units) and scopes it to one marketplace, a bounded period, and the marketplace's own currency. It explicitly separates itself from siblings by noting "The other reports leave Streaming TV out," so an agent can pick it over get_summary or the other report tools without opening a schema.

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?

Gives explicit selection criteria (Streaming TV only, one marketplace, max 31 days within the last 95 days) plus the reason to prefer it over other report tools. It also documents the two non-happy outcomes and their handling: pending means call again after meta.retry_after_seconds, unavailable means the account (e.g. KDP authors) has no Streaming TV access.

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

All Gloriads — Amazon Ads 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.

Resources

Need Help?