Skip to main content
Glama
alexdlaird

amazon-orders-mcp

by alexdlaird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_tracking

Read-only

Get the carrier and tracking number of a Shipment from its package tracking page.

Instructions

Get the carrier and tracking number of a Shipment from its package tracking page.

Input Schema

NameRequiredDescriptionDefault
siteNoThe 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_idYesThe Amazon Order ID of the Shipment.
shipment_idYesThe Shipment's `shipment_id`. Amazon stops showing the tracking link it comes from on older Orders.

Output Schema

NameRequiredDescriptionDefault
carrierNoThe carrier name, e.g. `UPS`, or `Amazon` for Amazon's own delivery network.
tracking_numberNoThe carrier's tracking number, e.g. `1Z999AA10123456784` or `TBA000000000000`. Always a `str`, since many (e.g. USPS) are all digits and may have leading zeros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • 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"
+}
  2. Addedv1.3.0

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 agent knows this is a safe external read. The description adds that data comes from scraping the package tracking page, which is mild context, but it doesn't mention failure modes (e.g., what happens when tracking is unavailable) or return shape. With annotations carrying the safety profile, a 3 fits.

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?

A single efficient sentence with the resource and source front-loaded. Every clause earns its place; nothing is wasted or buried.

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, annotations cover the safety and open-world profile, and parameters are fully documented in the schema. The description supplies the core purpose and source, so it is complete enough for correct invocation, with only minor room for failure-mode detail.

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 explains site, order_id, and shipment_id, including the note that Amazon hides tracking links on older orders. The description adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 ('Get') and resource ('carrier and tracking number of a Shipment'), and even names the source ('package tracking page'). It is clearly distinguishable from list-type siblings like get_order_history or get_order, though it doesn't explicitly name an alternative.

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 description (retrieve tracking info for a shipment), but there is no explicit when-to-use, when-not-to-use, or named alternative among the siblings. An agent must infer that this is the tool for tracking details rather than order details.

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

Deploy Server

Other Tools