Amazon SP-API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELLER_ID | Yes | Amazon Seller ID | |
| LWA_CLIENT_ID | Yes | Login with Amazon (LWA) OAuth 2.0 Client ID | |
| MARKETPLACE_ID | Yes | Amazon Marketplace ID (default: ATVPDKIKX0DER for US) | ATVPDKIKX0DER |
| SP_API_ENDPOINT | No | SP-API endpoint URL (optional, defaults to North America) | https://sellingpartnerapi-na.amazon.com |
| LWA_CLIENT_SECRET | Yes | Login with Amazon (LWA) OAuth 2.0 Client Secret | |
| LWA_REFRESH_TOKEN | Yes | Login with Amazon (LWA) OAuth 2.0 Refresh 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ordersB | Retrieve a list of orders from Amazon Seller Central. You can filter by date range, status, and fulfillment channel. Returns order summaries including order ID, status, total, and buyer info. |
| get_order_detailsA | Get detailed information about a specific Amazon order by order ID. Returns full order details including shipping address, buyer info, and order status. |
| get_order_itemsB | Get the line items (products) for a specific Amazon order. Returns details about each item including ASIN, SKU, quantity, price, and tax. |
| get_inventory_summaryB | Get FBA inventory summary including quantity available, reserved, inbound, and unfulfillable. Shows inventory health at a glance for all or specific SKUs. |
| get_fba_inventory_detailsB | Get detailed FBA inventory information including breakdown of reserved quantities, unfulfillable reasons, and researching quantities. Provides deeper insight into inventory status. |
| get_sales_metricsA | Get aggregated sales metrics from Amazon Sales API. USE THIS for longer date ranges (7+ days, 30 days, etc). IMPORTANT: Data has a 24-48 hour delay, so the last 2 days will NOT have data. For yesterday/today sales, use get_sales_summary instead. Returns total sales, unit count, order count grouped by day/week/month. |
| get_sales_summaryA | Get REAL-TIME sales summary calculated from orders data. USE THIS for yesterday/today sales (last 48 hours) since Sales API has a delay. Also useful when you need accurate recent data. Returns total sales, order count, units sold, and daily breakdown. |
| get_fba_reimbursementsA | Get FBA reimbursements for lost, damaged, or returned inventory within a date range. Shows reimbursement amounts, reasons, and affected products. Useful for tracking Amazon credits for inventory issues. |
| get_settlement_reportA | Get settlement report showing payment disbursements, including order sales, refunds, fees, and other charges. Provides detailed breakdown of what Amazon paid and deducted. |
| get_fba_fee_estimatesC | Get estimated FBA fees per SKU including referral fees, fulfillment fees, and other charges. Helpful for understanding per-unit costs and profitability analysis. |
| get_storage_feesA | Get FBA monthly storage fee charges by SKU. Shows storage costs, volume, and utilization for each product in Amazon fulfillment centers. |
| get_longterm_storage_feesB | Get long-term storage fees (LTSF) for inventory stored over 365 days. Shows aged inventory charges to help identify products incurring extra storage costs. |
| get_sales_traffic_reportB | Get detailed sales and traffic data including sessions, page views, conversion rate (unit session percentage), buy box percentage, and sales by ASIN. Essential for understanding product performance and conversion optimization. |
| get_search_terms_reportA | Get Brand Analytics search term report showing top search terms, search frequency rank, and click/conversion share by ASIN. Requires Brand Registry. Helps understand how customers find your products. |
| get_inventory_ledgerA | Get inventory ledger summary showing inventory movements including receipts, shipments, returns, adjustments, and balance changes over time. Helps track where inventory went. |
| get_catalog_itemB | Get detailed product information from the Amazon catalog by ASIN. Returns product title, brand, category, BSR (Best Sellers Rank), images, bullet points, and attributes. |
| search_catalogA | Search the Amazon catalog by keywords or identifiers (ASIN, SKU, UPC, EAN). Returns a list of matching items with summaries. Useful for finding products or looking up items by identifier. |
| get_financial_eventsB | Get financial events for a date range from Amazon Seller Central. Returns all financial events including sales, refunds, fees, reimbursements, and adjustments. Events are grouped by type for easy analysis. |
| get_financial_event_groupsA | Get financial event groups (payment disbursements) from Amazon Seller Central. Shows grouped financial events including fund transfers, account balances, and settlement periods. Useful for tracking payments and reconciliation. |
| get_order_financial_eventsA | Get all financial events for a specific Amazon order. Returns detailed financial breakdown including the sale amount, fees, taxes, shipping charges, and any adjustments for that order. |
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 20 tools
Tools are mostly distinct, with some closely related sales reporting functions (get_sales_metrics, get_sales_summary, get_sales_traffic_report) but descriptions clearly differentiate their use cases. No significant ambiguity.
All tools follow a consistent 'get_' prefix with descriptive noun phrases in lowercase with underscores. Pattern is uniform across the entire set.
20 tools cover the major areas of Amazon SP-API (catalog, inventory, orders, finances, sales) without being excessive. The count is well-scoped for the server's purpose.
Covers core seller operations comprehensively. Minor gaps exist (e.g., lack of listing management or FBA shipment creation), but the main workflows are supported.