amazon-orders-mcp

Overview Schema Source Related Servers Discussions Admin

get_order

Read-only

Retrieve complete details for a specific Amazon order by Order ID, with optional site selection, to inspect order information and answer order-related questions.

Instructions

Get the full details for a given Amazon Order ID.

Input Schema

Name	Required	Description	Default
`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`).
`order_id`	Yes	The Amazon Order ID to lookup.

Output Schema

Name	Required	Description
`index`	No	Where the Order appeared in the history when it was queried. This will inevitably change (e.g. when a new Order is placed, all indexes will then be off by one), but is still captured as it may be applicable in various use-cases. Populated when the Order was fetched through `get_orders` (use `start_index` to correlate), or when the `clone` has its `index` set.
`items`	No	The Order Items.
`subtotal`	No	The Order subtotal. Only populated when `full_details` is `True`.
`cancelled`	No	`True` if the Order was cancelled. When `True`, fields like `grand_total` and the totals on the details page may be `None` because Amazon stops rendering them.
`gift_card`	No	The Gift Card total (rendered as "Gift Card" on digital order details pages), as a negative amount. Only populated when `full_details` is `True`.
`gift_wrap`	No	The Gift Wrap total. Only populated when `full_details` is `True`.
`recipient`	No	The Order Recipients.
`shipments`	No	The Order Shipments.
`item_count`	No	The number of items in the purchase, when Amazon summarizes the count instead of listing the items (e.g. Whole Foods Market orders show "N items in this purchase"). `None` when no such summary is shown.
`grand_total`	No	The Order grand total.
`full_details`	No	If the Orders full details were populated from its details page.
`order_number`	No	The Order number. May be `None` only when the Order is `cancelled` and Amazon stripped the order number from the details page (the `order_number` parameter is used as a fallback in that case).
`refund_total`	No	The Order refund total. Only populated when `full_details` is `True`.
`estimated_tax`	No	The Order estimated tax. Only populated when `full_details` is `True`. For Whole Foods Market orders this is the "Tax and Fees" total from the receipt.
`free_shipping`	No	The Order free shipping, as a negative amount. Only populated when `full_details` is `True`.
`reward_points`	No	The Order reward points, as a negative amount of currency (not a count of points). Only populated when `full_details` is `True`.
`coupon_savings`	No	The Order coupon savings, as a negative amount. Only populated when `full_details` is `True`.
`is_whole_foods`	No	`True` if this is a Whole Foods Market purchase (an in-store/FOPO purchase or a Whole Foods receipt order). Unlike other unsupported order types, these expose a `grand_total` and (often) an `item_count` on the history page, so those fields are populated.
`payment_method`	No	The Order payment method. Only populated when `full_details` is `True`. For Whole Foods Market orders this is the card brand of the first payment method on the receipt (e.g. "Visa").
`shipping_total`	No	The Order shipping total. Only populated when `full_details` is `True`.
`amazon_discount`	No	The Amazon discount, as a negative amount. Only populated when `full_details` is `True`.
`total_before_tax`	No	The Order total before tax. Only populated when `full_details` is `True`.
`multibuy_discount`	No	The Multibuy discount, as a negative amount. Only populated when `full_details` is `True`.
`order_placed_date`	No	The Order placed date.
`promotion_applied`	No	The Order promotion applied, as a negative amount. Only populated when `full_details` is `True`.
`order_details_link`	No	The Order details link.
`payment_method_last_4`	No	The Order payment method's last 4 digits, preserved verbatim so leading zeros are not lost. Only populated when `full_details` is `True`.
`subscription_discount`	No	The Order Subscribe & Save discount, as a negative amount. Only populated when `full_details` is `True`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.0.1Oct 24, 2026

changedOutput schema / properties / index / description

Previous value: -"Where the Order appeared in the history when it was queried. This will inevitably change (e.g. when a new Order is placed, all indexes will then be off by one), but is still captured as it may be applicable in various use-cases. Populated when the Order was fetched through `get_order_history` (use `start_index` to correlate), or when the `clone` has its `index` set."New value: +"Where the Order appeared in the history when it was queried. This will inevitably change (e.g. when a new Order is placed, all indexes will then be off by one), but is still captured as it may be applicable in various use-cases. Populated when the Order was fetched through `get_orders` (use `start_index` to correlate), or when the `clone` has its `index` set."

changedOutput schema / properties / items / items / description

Previous value: -"An Item in an Amazon `Order`. If desired fields are populated as `None`, ensure `full_details` is `True` when retrieving the Order (for instance, with `get_order_history`), since by default it is `False` (it will slow down querying)."New value: +"An Item in an Amazon `Order`. If desired fields are populated as `None`, ensure `full_details` is `True` when retrieving the Order (for instance, with `get_orders`), since by default it is `False` (it will slow down querying)."

changedOutput schema / properties / shipments / items / properties / delivery_status / description

Previous value: -"The Shipment delivery status."New value: +"The Shipment delivery status, or `None` once Amazon stops showing it, some weeks after delivery."

changedOutput schema / properties / shipments / items / properties / items / items / description

Previous value: -"An Item in an Amazon `Order`. If desired fields are populated as `None`, ensure `full_details` is `True` when retrieving the Order (for instance, with `get_order_history`), since by default it is `False` (it will slow down querying)."New value: +"An Item in an Amazon `Order`. If desired fields are populated as `None`, ensure `full_details` is `True` when retrieving the Order (for instance, with `get_orders`), since by default it is `False` (it will slow down querying)."

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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns 'full details,' which signals completeness of the result, but it does not describe error behavior or any additional operational constraints.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple lookup tool and gets directly to the point.

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 the input schema fully documents the parameters. The description is complete enough for a simple read-by-ID tool, though it could mention how it relates to sibling list/search tools.

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 the schema already documents both order_id and site clearly, including the default-site behavior. The description only restates the order ID parameter and adds no further semantic detail, so the baseline score of 3 applies.

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 states a specific verb and resource: retrieving full details for a given Amazon Order ID. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as get_orders or search_orders.

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?

Usage is implied by the required order ID, suggesting the tool is for looking up a single known order. However, there is no explicit guidance on when to use this instead of get_orders, search_orders, or get_tracking.

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

Deploy Server