Skip to main content
Glama

search_orders

Read-only

Search every year of Amazon order history by product title, order number, address, or recipient, and get each matching item with its order number and date.

Instructions

Search every year of the Order history for Orders by product title, Order number, address, or recipient, as the search box on Your Orders does, getting each matching Item with its Order's number and date.

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`).
limitNoStop fetching result pages once at least this many results are collected. Whole pages are fetched, so the batch can hold up to a page more than `limit`. `None` fetches every page.
queryYesWhat to search for: words from a product title, an Order number, or a name or address an Order was sent to.
cursorNoThe `cursor` of the previous batch, to fetch the next one.

Output Schema

NameRequiredDescriptionDefault
itemsNoThe results in this batch.
cursorNoPass 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_moreNo`True` if there are more results to fetch with `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A3.8/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. The description adds useful context by stating that it searches every year of order history and returns each matching Item with its Order number and date.

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 that clearly conveys scope, search inputs, and result content without unnecessary wording.

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?

Given full schema coverage, an output schema, and annotations covering safety and openness, the description provides enough context to call the tool correctly. It could be stronger only by explicitly situating this tool relative to its siblings.

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 parameters are already well documented. The description reinforces the query semantics but adds little beyond what the schema already provides for site, limit, and cursor.

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 gives a specific verb and resource: search Order history for Orders by product title, Order number, address, or recipient. It clearly states the search scope and result shape, though it does not explicitly distinguish itself from sibling tools like get_orders or get_order.

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 usage by explaining what can be searched and comparing the behavior to the search box on Your Orders. However, it gives no explicit guidance on when to use this tool versus get_orders, get_order, or other siblings.

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