amazon-orders-mcp

Overview Schema Source Related Servers Discussions Admin

get_transactions

Read-only

Get a batch of Amazon Transaction history for a given number of days, or for a single Order, with a cursor to fetch the next batch.

Instructions

Get a batch of Amazon Transaction history for a given number of days, or for a single Order, with a cursor to fetch the next batch.

Input Schema

Name	Required	Description
`days`	No	The number of days worth of Transactions to get. Ignored when `order_id` or `cursor` is given.
`site`	No	The Amazon site to read, e.g. `amazon.de`, since each site has its own orders. By default, the user's default site (see `check_session`).
`limit`	No	Stop fetching Transaction pages once at least this many Transactions are collected. Whole pages are fetched, so the batch can hold up to a page more than `limit`. `None` fetches every page.
`cursor`	No	The `cursor` of the previous batch, to fetch the next one. The `days` window or `order_id` it was fetched with carries over.
`order_id`	No	If given, only Transactions for this Amazon Order ID are returned, as in `get_transactions`. Ignored when `cursor` is given.

Output Schema

Name	Required	Description
`items`	No	The results in this batch.
`cursor`	No	Pass this back as `cursor` to the same call to fetch the next batch. A JSON-safe `dict` to keep as it is, not to build or change. `None` when there are no more results.
`has_more`	No	`True` if there are more results to fetch with `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.2Oct 22, 2026

addedInput schema / properties / site

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The Amazon site to read, e.g. `amazon.de`, since each site has its own orders. By default, the user's default site (see `check_session`).",
+  "title": "Site"
+}

First observedv1.2.0Oct 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds that results come in batches with a cursor for the next batch, which is real behavioral context beyond the annotations' scope. It stops short of describing ordering, freshness, or failure behavior.

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?

A single sentence that front-loads the verb and resource and then enumerates the modes plus pagination. Dense but every clause carries information; slightly run-on but not wasteful.

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 no explanation, and all five parameters are fully described in the schema. The description covers the modal selection and pagination, leaving only tool-routing against siblings unaddressed.

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% and every parameter is documented in detail there, including the cursor carry-over and the limit page-rounding semantics. The description only restates the three modes, so the baseline 3 applies with no meaningful added semantics.

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?

States a specific verb and resource ('Get a batch of Amazon Transaction history') plus the three access modes: day window, single order, cursor batch. It does not name any sibling tool, so an agent cannot distinguish it from get_order_history or get_order without reading further, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

The description implies the three usage modes (days, order_id, cursor) but never states when to prefer this tool over get_order_history or get_order, nor any prerequisites beyond what the schema states. Usage is implied by the parameter modes rather than explained.

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

Deploy Server