Tool Reference
Finance Tools
Payment transactions, fee breakdowns, profitability signals, and settlement economics.
Related paths
Hosted Amazon Seller Central MCP overview for Claude, ChatGPT, and custom agents.
Amazon seller data layerHow ads, inventory, orders, catalog, ranking, finance, and fulfillment data are structured for agents.
Claude connection walkthroughStep-by-step path from Seller Central OAuth to a Claude connector or MCP config.
ChatGPT Seller Central setupChatGPT-specific setup and examples for Amazon seller data through MCP.
Tools (4)
read
get_financial_events
readGet Finances v0 financial-event fee components by ASIN/order grain and ASIN profitability views by financial-event posted_date.
When to use
Use this for financial-event fee components, order-level fee exports, or ASIN economics. Use get_payment_transactions for pre-settlement Transaction View rows and get_settlement_economics for finalized settlement report rows.
Parameters10
| Name | Type | Description |
|---|---|---|
view | enum (fee_breakdown) | fee_breakdown returns fee components by the selected grain; profitability returns ASIN revenue/fee/net rows. |
grain | enum (asin) | fee_breakdown view only. asin returns the existing ASIN pivot; order_item returns one row per posted_date/order_id/ASIN/SKU/event_type with common fee columns; raw_component returns one row per fee component across the date range. |
order_id | string | fee_breakdown view only. Specific order ID returns raw component rows. |
asin | string | Filter by ASIN. |
start_date | string (90 days ago) | Financial-event posted_date start date (YYYY-MM-DD). Defaults to 90 days ago. |
end_date | string (today) | Financial-event posted_date end date (YYYY-MM-DD). Defaults to today. |
sort_by | enum | Sort column. Allowed columns depend on view/order_id mode. |
sort_order | enum (desc) | Sort direction: asc or desc. |
limit | number (20) | Max rows to return (1-1000). |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
Tips
- Use view="fee_breakdown" plus order_id for raw fee component rows on a known order.
- Use view="fee_breakdown" with grain="order_item" for bulk weekly order-level exports that need order_id, ASIN, SKU, revenue, fees, tax, and net by posted_date.
- Use view="fee_breakdown" with grain="raw_component" when the agent needs every component row instead of pivoted fee columns.
- Use view="fee_breakdown" without grain or with grain="asin" for the existing ASIN fee pivots across the posted_date range.
- Use view="profitability" for ASIN-level revenue, fees, tax, net profit, units, and data-gap fields.
Watch out
- Date filters use financial-event posted_date, not customer purchase date.
get_profitability_review
readReturn profitability issue signals by ASIN from financial-event net, FBA reimbursements, returns, Business Reports units, and SP/SD ad spend.
When to use
Inspect ASIN-level profitability states across contribution, ad spend, fees, returns, and reimbursements.
Parameters11
| Name | Type | Description |
|---|---|---|
asin | string | Filter by ASIN. |
sku | string | Filter by SKU. |
start_date | string (30 days ago) | Start date (YYYY-MM-DD). Defaults to 30 days ago. |
end_date | string (today) | End date (YYYY-MM-DD). Defaults to today. |
review_focus | enum (all) | Issue to focus: all, negative_contribution, ad_drag, fee_pressure, high_return_rate, reimbursement_reliance, low_margin. |
target_margin_pct | number (20) | Contribution margin below this percent is flagged as low_margin. |
high_tacos_pct | number (15) | SP/SD ad spend above this percent of sales is flagged as ad_drag. |
high_fee_pct | number (35) | Amazon fees above this percent of gross revenue are flagged as fee_pressure. |
high_return_rate_pct | number (10) | Returned units above this percent of units ordered are flagged as high_return_rate. |
include_healthy | boolean (false) | Include healthy ASINs after profitability issues. |
limit | number (20) | Max rows to return (1-100). |
Tips
- Sorts by issue score so negative contribution, ad drag, high fees, return pressure, and reimbursement reliance surface first.
- Use review_focus to isolate one issue type when you already know what you are investigating.
- Pair with get_financial_events, get_returns, and get_tacos to inspect the highest-risk ASINs in detail.
Watch out
- Contribution is financial-event marketplace net + FBA reimbursements - SP/SD ad spend.
- COGS, inbound freight, storage fees without ASINs, and Sponsored Brands spend are not included.
get_settlement_economics
readGet settlement-report finalized financial data. Summary mode (default): pivoted per-ASIN economics with revenue, referral fees, FBA fees, storage fees. Detail mode: raw settlement rows filtered by amount type.
When to use
Analyze finalized settlement data for per-ASIN economics including storage fees and promotions, or get raw settlement rows for settlement reconciliation. Use get_payment_transactions for recent Payments Transaction View rows before settlement finalization.
Parameters10
| Name | Type | Description |
|---|---|---|
asin | string | Filter by ASIN. |
sku | string | Filter by SKU. |
sort_order | enum (desc) | Sort direction: asc or desc. |
limit | number (20) | Max rows to query (1-1000). Use a higher limit when the user asks for all matching rows; large responses are capped automatically. |
start_date | string | Start date (YYYY-MM-DD) for posted_date. |
end_date | string | End date (YYYY-MM-DD) for posted_date. |
amount_type | string | Filter by amount type (e.g. ItemPrice, ItemFees, Promotion). Only applies in detail mode. |
detail | boolean (false) | true = raw settlement rows, false = pivoted per-ASIN summary. |
sort_by | enum (revenue) | Column to sort by: asin, revenue, total_fees, net, quantity_purchased. |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
Tips
- Use summary mode (default) for a quick per-ASIN economic overview.
- Use detail mode with amount_type filter for reconciliation against specific fee types.
- Storage fees appear in the summary mode, unlike get_financial_events which only has transaction-level fees.
- For recent refund, deferred, or payment rows before settlement close, use get_payment_transactions instead.
Watch out
- Settlement reports can lag live Payments transactions until Amazon finalizes the settlement period.
live api
get_payment_transactions
live apiGet live Amazon Payments / Transaction View-style transactions from SP-API Finances v2024. Returns transaction rows or grouped summaries with transaction type, status, amounts, related identifiers, visible item context, and source coverage notes.
When to use
Use this for recent payment, refund, or deferred transaction rows before settlement reports finalize, or to inspect Payments Transaction View-style facts by date range or order ID.
Parameters11
| Name | Type | Description |
|---|---|---|
start_date | string (30 days ago) | Start date (YYYY-MM-DD) for postedDate. Defaults to 30 days ago when order_id is omitted. |
end_date | string (today) | End date (YYYY-MM-DD) for postedDate. Defaults to today when order_id is omitted; postedBefore is capped to Amazon's three-minute requirement. |
transaction_type | string | Exact transactionType filter applied locally, for example Refund, Shipment, ServiceFee, or FBAInventoryReimbursement. |
transaction_status | enum | Amazon transaction status: DEFERRED, RELEASED, or DEFERRED_RELEASED. |
order_id | string | Amazon order ID. When supplied, the tool uses Amazon's ORDER_ID related identifier filter instead of postedAfter/postedBefore. |
marketplace_id | string | Optional marketplace ID assertion. If supplied, it must match the account's configured marketplace. The tool always queries the account's marketplace. |
detail | boolean (false) | true = transaction rows; false = grouped summary by date, transaction type, status, and currency. |
sort_by | enum (posted_date) | Sort by posted_date, total_amount, transaction_type, or transaction_status. |
sort_order | enum (desc) | Sort direction: asc or desc. |
limit | number (100) | Maximum matching transactions to fetch before summary/detail formatting (1-500). |
include_raw_rows | boolean (true) | Set false to return a compact row preview. Defaults to true; large result sets are capped automatically to keep the response manageable. |
Tips
- Use transaction_type="Refund" for recent refund rows that may not appear in settlement reports yet.
- Use transaction_status to separate DEFERRED, RELEASED, and DEFERRED_RELEASED payment transactions.
- Set detail=true when you need transaction identifiers, related order/refund/settlement IDs, or item-level ASIN/SKU context.
Watch out
- Amazon notes financial events might not include orders from the last 48 hours.
- postedBefore is capped to more than three minutes before request time when the selected end date reaches the current time.
- transaction_type is filtered locally because listTransactions does not expose a transactionType query parameter.
- The tool fails closed if the account has no configured marketplace or if a supplied marketplace_id differs. There is no US/default fallback.