Amazon Seller MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SP_API_ENDPOINT | No | Regional endpoint for your marketplace (default EU, used by India) | https://sellingpartnerapi-eu.amazon.com |
| SP_API_CLIENT_ID | Yes | LWA app client ID (amzn1.application-oa2-client...) | |
| SP_API_SELLER_ID | Yes | Merchant Token (Seller ID, starts with A) | |
| SP_API_CLIENT_SECRET | Yes | LWA app client secret | |
| SP_API_REFRESH_TOKEN | Yes | Long-lived refresh token (a long opaque string) | |
| SP_API_MARKETPLACE_ID | No | Marketplace ID (default India A21TJRUUN4KGV) | A21TJRUUN4KGV |
| SP_API_TOKEN_ENDPOINT | No | LWA token endpoint (default https://api.amazon.com/auth/o2/token) | https://api.amazon.com/auth/o2/token |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_seller_profileA | Returns the seller's marketplace participations (store name, marketplace, currency, participation status). |
| list_listingsA | Real-time list of catalogued SKUs for the seller (searchListingsItems). Paginates through all pages. |
| get_listingA | Full details for one SKU: summaries (ASIN/status), attributes, offers, issues, and fulfillment availability. |
| upsert_listingA | Creates or updates a listing via PUT. Provide productType, sku, and the full attributes object. Use requirements=LISTING for a complete/offer listing or LISTING_PRODUCT_ONLY for a product-only draft. |
| set_quantityB | Sets the fulfillment quantity for a SKU (merchant-fulfilled / DEFAULT channel). |
| delete_listingA | DESTRUCTIVE: permanently deletes the listing for a SKU. Requires confirm=true. Tip: if the listing has an active offer, set quantity to 0 first, then delete. |
| update_priceA | Convenience: sets the selling price (and optional MRP) for a SKU via a purchasable_offer PATCH, without a full upsert. |
| get_product_type_definitionA | Fetches the product type definition metadata (includes a link to the JSON schema with required attributes and enums). |
| get_ordersA | Lists orders. Defaults to orders created in the last 30 days. Note: full buyer/address data requires the restricted PII role. |
| get_order_itemsC | Returns the line items for a specific order. |
| request_reportA | Creates a report request and returns a reportId. Example types: GET_MERCHANT_LISTINGS_ALL_DATA, GET_FLAT_FILE_OPEN_LISTINGS_DATA, GET_FBA_INVENTORY_PLANNING_DATA. |
| get_reportA | Returns a report's processing status. When DONE, use the reportDocumentId with download_report. |
| download_reportB | Downloads and decompresses a report document by its reportDocumentId, returning the text. |
| submit_feedA | Submits a feed in one call: creates a feed document, uploads the content, and creates the feed. Common for flat-file / JSON_LISTINGS_FEED bulk operations. Returns the feedId to poll with get_feed. This WRITES to your account. |
| get_feedC | Returns a feed's processing status. When DONE, use resultFeedDocumentId with download_report-style retrieval. |
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 15 tools
Most tools have distinct purposes and clear descriptions. Potential confusion between get_orders and get_order_items (one lists orders, the other fetches line items for a specific order) is mitigated by context, but get_ and list_ verbs could be more consistently separated.
Names generally follow verb_noun pattern with verbs like get, list, upsert, set, delete, update, request, submit. Minor inconsistency: list_ is used for plural collections (list_listings, list_orders) while get_ is used for singular resources, but get_orders is plural and list_listings is plural, creating slight overlap.
15 tools is at the upper bound of the ideal range. They cover a reasonable breadth of seller operations (profile, listings, orders, reports, feeds) without being overwhelming, though some consolidation could be considered.
The tool set covers major listing CRUD, order listing, report/feed submission and retrieval. Missing a dedicated 'get_order' for full order details (only line items are available) and no order update/shipment actions, but core workflows are represented.