amazon-orders-mcp

Overview Schema Source Related Servers Discussions Admin

get_gift_cards

Read-only

Retrieve Amazon Gift Card balance and recent activity for a chosen site and day range, with cursor-based paging to fetch additional batches.

Instructions

Get the Amazon Gift Card balance, and a batch of its activity for a given number of days, with a cursor to fetch the next batch.

Input Schema

Name	Required	Description
`days`	No	The number of days worth of Gift Card activity to get. Ignored when `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 activity pages once at least this many GiftCardActivity entries 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 it was fetched with carries over.

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.
`balance`	No	The current Gift Card balance, or `None` if Amazon didn't show one.
`has_more`	No	`True` if there are more results to fetch with `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.1Oct 24, 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 and openWorldHint, so the safety profile is covered. The description adds useful pagination behavior (batches plus a cursor for the next batch), but says nothing about auth expectations, rate limits, or what happens when no gift cards exist.

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 sentence that front-loads the primary resource (balance) and then the secondary payload (activity batch + cursor). No filler, no restatement of the title.

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 the pagination model is captured. What remains missing is any note about prerequisites such as an authenticated session or how site defaults are resolved, though the schema's site parameter covers that partially.

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 days, site, limit, and cursor are all fully documented in the schema itself. The description restates the days-window and cursor-batch concepts without adding syntax, ranges, or edge-case guidance beyond what the schema already gives.

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 concrete verb and resource plus the two things returned: the gift card balance and a batch of activity, with cursor-based batching. That is clearly distinguishable from siblings like get_transactions or get_orders, though the description never names those alternatives explicitly.

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 only implied – the reader must infer this is the tool for gift card balance/history rather than get_transactions. There is no explicit when-to-use, when-not-to-use, or named alternative, even though nearby siblings cover overlapping financial data.

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

Deploy Server