Amazon Orders MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List saved Amazon account profiles, session status, and last sync time. |
| login_accountA | Open a browser window to log into an Amazon account. Saves the session for future order fetches. Complete sign-in and 2FA manually in the browser. |
| sync_ordersA | Import orders from Amazon into the local database. Only fetches orders not already stored (plus recent orders for status/tracking updates). |
| get_ordersA | Read orders from the local database (run sync_orders first to populate). Returns item name, order date, tracking number, and order status per item. |
| remove_accountB | Delete a saved account profile, its browser session, and cached orders. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct action and target: list_accounts (read accounts), login_account (authenticate), sync_orders (import), get_orders (read local orders), remove_account (delete account). No overlapping purposes; descriptions clarify the read/write split between sync_orders and get_orders.
All tools use snake_case with a verb_noun pattern (list_accounts, login_account, sync_orders, get_orders, remove_account). Singular/plural noun variations (account vs accounts) are minor and do not break the pattern.
5 tools appropriately cover the core account and order management workflows without redundancy or excessive granularity. This is well within the ideal 3-15 range for a focused MCP server.
Core account lifecycle (list, login, remove) and order workflow (sync, get) are covered. Minor gaps exist: no tool to retrieve a single order by ID or search orders, and sync/get operations do not explicitly target a specific account, requiring workarounds via login switches.