Skip to main content
Glama

get_orders

Read-only

List individual orders (last N days): order ids, status, dates and totals only — no buyer data. Live Amazon Orders API, throttled (≈1 req/min): use ONLY when you need order-level rows. For daily sales/orders charts or trends over a period use get_daily_sales; for a single revenue total use get_revenue_summary — both are served from cache and never throttle.

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_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax orders returned (most recent first). Omit for all.
statusesNoStati ordine Amazon da includere (array, es. ["Shipped","Unshipped"]).
days_backNoQuanti giorni indietro partire da oggi (intero, es. 30).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / days_back / description
      Added value: +"Quanti giorni indietro partire da oggi (intero, es. 30)."
    • addedInput schema / properties / statuses / description
      Added value: +"Stati ordine Amazon da includere (array, es. [\"Shipped\",\"Unshipped\"])."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

On top of annotations that already mark this read-only and non-destructive, the description discloses that this hits the live Amazon Orders API, is throttled at roughly 1 request per minute, and returns no buyer data. The rate limit and data-scope note are exactly the behavioral context annotations cannot carry.

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?

Three compact sentences, front-loaded with what is returned and the throttling caveat before routing to alternatives. Every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description compensates by enumerating the returned fields and their exclusions, and it covers the throttle risk that affects call planning. For a 4-parameter, fully documented read tool, nothing required for correct invocation is missing.

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 all four parameters (limit, statuses, days_back, account_id) are already documented in the schema. The description only restates the day-range scoping that days_back already covers and adds nothing about defaults or account_id selection. Baseline 3 applies when the schema does the heavy lifting.

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 ("List individual orders") plus the time window (last N days) and the exact fields returned (order ids, status, dates, totals), explicitly excluding buyer data. This is enough to distinguish it from nearby order and reporting siblings 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 an explicit inclusion rule ("use ONLY when you need order-level rows") and names two alternatives with the conditions that select them: get_daily_sales for daily charts/trends and get_revenue_summary for a single revenue total. It even explains why those alternatives are preferable (cached, never throttle).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources