Gloriads — Amazon Ads

Figures by placement and off Amazon

get_placements_report

Read-onlyIdempotent

Get each ad type's figures by placement (top of search, rest of search, product pages, off Amazon) over a period, and what Sponsored Products spent and sold OFF Amazon (other sites, apps, creators' content) per marketplace, with its share of the Sponsored Products spend: the dashboard's « Performance by placement » and « Spend off Amazon » cards, in USD. Amazon's console shows no off-Amazon figures. Answers "how much do my ads spend outside Amazon?", "is off-Amazon traffic worth it?" or "which placement has the best ACOS?". With compare, each placement's compared figures. Amounts are in USD (Amazon converts each marketplace). meta.data_last_date says up to which day the figures go.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_placements_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.
`compare`	No	"previous_period" (the same number of days just before; "this_month" against the same days of last month) or "same_period_last_year" (the same dates a year earlier). Adds the compared period's figures and how each changed (the dashboard's "+18 %"). Both periods then end yesterday. Absent: no comparison.
`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.
`marketplaces`	No	Keep only these marketplaces, by country code: US, CA, MX, BR, UK, DE, FR, ES, IT, NL, SE, PL, BE, TR, AE, SA, EG, IN, ZA, JP, AU, SG. Absent: every marketplace.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: all amounts are USD with Amazon's per-marketplace conversion, comparison periods both end yesterday, and `meta.data_last_date` reports data freshness. It does not discuss row limits, pagination, or granularity of the returned series, which keeps it short of a 5.

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

Conciseness3/5

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

The core purpose leads, but the text is dense and repetitive: "off Amazon" spend is described twice, currency is stated twice ("in USD" and parenthetical "Amounts are in USD"), and the parenthetical marketplace list duplicates the schema enum. It is informative but not tightly written.

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 no output schema and six optional parameters, the description does the necessary work: it names the two dashboard cards being reproduced, lists the placement breakdown, explains the off-Amazon spend/share output, and points at `meta.data_last_date` for freshness. Only return shape details like row structure or ordering are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning on top by explaining that with `compare` each placement carries compared figures and change values, and by framing the whole result set as per-marketplace USD. The remaining parameters (range, dates, timezone) are only echoed from the schema rather than extended.

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: each ad type's figures by placement (top of search, rest of search, product pages, off Amazon) plus Sponsored Products spend/sales off Amazon per marketplace with its spend share. It also anchors itself to two named dashboard cards, so an agent can distinguish it from get_summary or get_products_report without inspecting schemas.

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?

Gives explicit triggering questions ("how much do my ads spend outside Amazon?", "which placement has the best ACOS?") and states a key usage fact: Amazon's own console shows no off-Amazon figures, which is precisely when to prefer this tool. It does not, however, name any sibling tool as an alternative or state exclusions against get_summary/get_products_report.

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?