Agent Central

Settlement economics

get_settlement_economics

Read-only

Get settlement-report finalized financial data. This tool is backed by settlement reports and can lag recent Payments / Transaction View rows until Amazon finalizes the settlement period; use get_payment_transactions for recent refund, deferred, or payment transaction rows before settlement finalization. Summary mode (default): pivoted economics by ASIN when resolvable, otherwise by SKU, including source-signed order_item_price, refund_item_price, refund_net, principal quantity, and FBAPerUnitFulfillmentFee amount/quantity/per-unit value. revenue remains all ItemPrice rows for backward compatibility. The per-unit fulfillment fee is signed like the settlement fee amount. Summary fee fields commission (Amazon's referral fee, from amount_description Commission), item_fees (all item-level fees: commission, fulfillment, refund/shipping/giftwrap chargebacks), fba_fee, and fba_per_unit_fulfillment_fee overlap and are not additive; use net or total_fees for period totals. Summary mode also returns unattributed_fees: account-level settlement-report fees (AWD, removal orders, Deal/Vine/Premium Services, quarterly returns fees) that carry no SKU and cannot be attributed to an ASIN, grouped by fee type with a total (these are excluded from the per-ASIN pivot). This is a date-window ASIN analysis, not an exact Amazon disbursement statement: a window can contain multiple settlement IDs, and transaction families present in the live Payments feed might be absent from the V2 settlement report. For exact finalized disbursement-group reconciliation, use get_payment_transactions with financial_event_group_id and transaction_status=RELEASED, following pagination until complete. Detail mode: raw settlement-report rows filtered by amount type or amount description. settlement_effective_date uses posted_date, then posted_date_time, settlement_end_date, deposit_date, and finally snapshot_date because Amazon settlement rows can omit posted_date. marketplace_currency is inferred from the scoped Amazon marketplace when settlement item rows omit currency. asin_resolution explains how ASIN was attached to settlement rows: order_item_asin comes from the order item table and is preferred when available; historical_sku_asin comes from historical order-item SKU maps; active_listing_sku comes from active-listing SKU maps; settlement_text_asin parses an ASIN embedded in the fee text (for example FBA customer-returns fees). Rows that cannot be mapped to an ASIN are still returned at SKU grain instead of being suppressed. Currency note: settlement rows do not carry a reliable per-row currency, so marketplace_currency is asserted from the scoped marketplace and amounts are not currency-filtered; if the account transacts in multiple currencies (e.g. a North America unified account) settlement amounts may combine currencies, so use get_financial_events (scoped to the marketplace currency by default) to isolate a single currency.

Input Schema

Name	Required	Description	Default
`sku`	No	Filter by SKU
`asin`	No	Filter by ASIN
`limit`	No	Max rows (1-1000, default 20).
`detail`	No	true = raw settlement rows, false = pivoted per-ASIN summary
`offset`	No	Pagination offset (0-100000, default 0). Use the returned pagination.next_offset to continue.
`sort_by`	No	Column to sort by (summary mode)	revenue
`end_date`	No	Optional. YYYY-MM-DD end date for settlement_effective_date. The range may span at most 366 days.
`sort_order`	No	Sort order	desc
`start_date`	No	Optional. YYYY-MM-DD start date for settlement_effective_date. The range may span at most 366 days.
`amount_type`	No	Detail mode only. Filter by amount type (e.g. ItemPrice, ItemFees, Promotion).
`include_raw_rows`	No	For tabular results, false returns compact rows capped at MCP_TEXT_ROW_PREVIEW_LIMIT (default 10), regardless of limit. Complete-page and custom non-tabular responses may ignore this option; see tool-specific notes. Default true; large full-row responses are capped separately. Freshness fields require include_diagnostics=true in either row mode, where supported.
`amount_description`	No	Detail mode only. Filter by amount description (e.g. FBAPerUnitFulfillmentFee).
`include_diagnostics`	No	True enables expanded freshness diagnostics. Where supported, snapshot_capture_at and snapshot_data_through_date are populated only when include_diagnostics=true, in both compact and full-row modes; values may still be null if source data is unavailable. Default false. Basic empty-result data-window diagnostics are included by default when available.

Output Schema

Name	Required	Description	Default
`evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedNov 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / evidence / properties / effective_scope / $ref
```
Removed value: -"#/properties/evidence/properties/requested_scope"
```
addedOutput schema / properties / evidence / properties / effective_scope / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / evidence / properties / effective_scope / properties

Added value: +{
+  "end_date": {
+    "anyOf": [
+      {
+        "format": "date",
+        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "filters": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "group_by": {
+    "items": {
+      "maxLength": 128,
+      "minLength": 1,
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "marketplace_id": {
+    "anyOf": [
+      {
+        "minLength": 1,
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "reporting_time_zone": {
+    "anyOf": [
+      {
+        "minLength": 1,
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "sort": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "direction": {
+          "enum": [
+            "asc",
+            "desc"
+          ],
+          "type": "string"
+        },
+        "field": {
+          "maxLength": 128,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "field",
+        "direction"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "start_date": {
+    "anyOf": [
+      {
+        "format": "date",
+        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedOutput schema / properties / evidence / properties / effective_scope / required

Added value: +[
+  "marketplace_id",
+  "start_date",
+  "end_date",
+  "reporting_time_zone",
+  "group_by",
+  "sort",
+  "filters"
+]

addedOutput schema / properties / evidence / properties / effective_scope / type
```
Added value: +"object"
```
removedOutput schema / properties / evidence / properties / grain / items / $ref
```
Removed value: -"#/properties/evidence/properties/tool"
```
addedOutput schema / properties / evidence / properties / grain / items / maxLength
```
Added value: +128
```
addedOutput schema / properties / evidence / properties / grain / items / minLength
```
Added value: +1
```
addedOutput schema / properties / evidence / properties / grain / items / type
```
Added value: +"string"
```
removedOutput schema / properties / evidence / properties / join_keys / items / properties / field / $ref
```
Removed value: -"#/properties/evidence/properties/tool"
```
addedOutput schema / properties / evidence / properties / join_keys / items / properties / field / maxLength
```
Added value: +128
```
addedOutput schema / properties / evidence / properties / join_keys / items / properties / field / minLength
```
Added value: +1
```
addedOutput schema / properties / evidence / properties / join_keys / items / properties / field / type
```
Added value: +"string"
```

changedOutput schema / properties / evidence / properties / observed / properties / data_start / anyOf

Previous value: -[
-  {
-    "format": "date",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / evidence / properties / observed / properties / data_through / anyOf

Previous value: -[
-  {
-    "format": "date",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / evidence / properties / requested_scope / properties / end_date / anyOf

Previous value: -[
-  {
-    "format": "date",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / evidence / properties / requested_scope / properties / filters / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / evidence / properties / requested_scope / properties / group_by / items / $ref
```
Removed value: -"#/properties/evidence/properties/tool"
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / group_by / items / maxLength
```
Added value: +128
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / group_by / items / minLength
```
Added value: +1
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / group_by / items / type
```
Added value: +"string"
```
removedOutput schema / properties / evidence / properties / requested_scope / properties / sort / items / properties / field / $ref
```
Removed value: -"#/properties/evidence/properties/tool"
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / sort / items / properties / field / maxLength
```
Added value: +128
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / sort / items / properties / field / minLength
```
Added value: +1
```
addedOutput schema / properties / evidence / properties / requested_scope / properties / sort / items / properties / field / type
```
Added value: +"string"
```

changedOutput schema / properties / evidence / properties / requested_scope / properties / start_date / anyOf

Previous value: -[
-  {
-    "format": "date",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / end_date / description

Previous value: -"Optional. YYYY-MM-DD end date for settlement_effective_date."New value: +"Optional. YYYY-MM-DD end date for settlement_effective_date. The range may span at most 366 days."

changedInput schema / properties / start_date / description

Previous value: -"Optional. YYYY-MM-DD start date for settlement_effective_date."New value: +"Optional. YYYY-MM-DD start date for settlement_effective_date. The range may span at most 366 days."

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / include_diagnostics / description

Previous value: -"True may add expanded freshness diagnostics. Basic empty-result data-window diagnostics are included by default when available."New value: +"True enables expanded freshness diagnostics. Where supported, snapshot_capture_at and snapshot_data_through_date are populated only when include_diagnostics=true, in both compact and full-row modes; values may still be null if source data is unavailable. Default false. Basic empty-result data-window diagnostics are included by default when available."

changedInput schema / properties / include_raw_rows / description

Previous value: -"False returns compact rows. Default true."New value: +"For tabular results, false returns compact rows capped at MCP_TEXT_ROW_PREVIEW_LIMIT (default 10), regardless of limit. Complete-page and custom non-tabular responses may ignore this option; see tool-specific notes. Default true; large full-row responses are capped separately. Freshness fields require include_diagnostics=true in either row mode, where supported."

Changed5 schema fields changedOct 27, 2026

changedOutput schema / properties / evidence / properties / basis / properties / date / items / enum

Previous value: -[
-  "order_date",
-  "reporting_date",
-  "click_attribution_date",
-  "posted_date",
-  "settlement_date",
-  "snapshot_date",
-  "live_observation_time",
-  "event_time",
-  "effective_date",
-  "not_applicable",
-  "not_reported"
-]New value: +[
+  "order_date",
+  "reporting_date",
+  "click_attribution_date",
+  "posted_date",
+  "financial_event_group_start",
+  "settlement_date",
+  "snapshot_date",
+  "live_observation_time",
+  "event_time",
+  "effective_date",
+  "not_applicable",
+  "not_reported"
+]

changedOutput schema / properties / evidence / properties / entity_types / items / enum

Previous value: -[
-  "account",
-  "marketplace",
-  "product",
-  "variation_family",
-  "listing",
-  "offer",
-  "inventory_item",
-  "fulfillment_center",
-  "order",
-  "order_item",
-  "campaign",
-  "ad_group",
-  "ad",
-  "target",
-  "keyword",
-  "search_query",
-  "portfolio",
-  "store",
-  "audience_segment",
-  "dsp_advertiser",
-  "shipment",
-  "inbound_plan",
-  "fulfillment_operation",
-  "transaction",
-  "settlement",
-  "financial_event",
-  "return",
-  "reimbursement",
-  "promotion",
-  "review",
-  "catalog_definition",
-  "audit_event",
-  "not_applicable"
-]New value: +[
+  "account",
+  "marketplace",
+  "product",
+  "variation_family",
+  "listing",
+  "offer",
+  "inventory_item",
+  "fulfillment_center",
+  "order",
+  "order_item",
+  "campaign",
+  "ad_group",
+  "ad",
+  "target",
+  "keyword",
+  "search_query",
+  "portfolio",
+  "store",
+  "audience_segment",
+  "dsp_advertiser",
+  "shipment",
+  "inbound_plan",
+  "fulfillment_operation",
+  "transaction",
+  "settlement",
+  "financial_event",
+  "financial_event_group",
+  "return",
+  "reimbursement",
+  "promotion",
+  "review",
+  "catalog_definition",
+  "audit_event",
+  "not_applicable"
+]

changedOutput schema / properties / evidence / properties / join_keys / items / properties / entity_type / enum

Previous value: -[
-  "account",
-  "marketplace",
-  "product",
-  "variation_family",
-  "listing",
-  "offer",
-  "inventory_item",
-  "fulfillment_center",
-  "order",
-  "order_item",
-  "campaign",
-  "ad_group",
-  "ad",
-  "target",
-  "keyword",
-  "search_query",
-  "portfolio",
-  "store",
-  "audience_segment",
-  "dsp_advertiser",
-  "shipment",
-  "inbound_plan",
-  "fulfillment_operation",
-  "transaction",
-  "settlement",
-  "financial_event",
-  "return",
-  "reimbursement",
-  "promotion",
-  "review",
-  "catalog_definition",
-  "audit_event",
-  "not_applicable"
-]New value: +[
+  "account",
+  "marketplace",
+  "product",
+  "variation_family",
+  "listing",
+  "offer",
+  "inventory_item",
+  "fulfillment_center",
+  "order",
+  "order_item",
+  "campaign",
+  "ad_group",
+  "ad",
+  "target",
+  "keyword",
+  "search_query",
+  "portfolio",
+  "store",
+  "audience_segment",
+  "dsp_advertiser",
+  "shipment",
+  "inbound_plan",
+  "fulfillment_operation",
+  "transaction",
+  "settlement",
+  "financial_event",
+  "financial_event_group",
+  "return",
+  "reimbursement",
+  "promotion",
+  "review",
+  "catalog_definition",
+  "audit_event",
+  "not_applicable"
+]

changedOutput schema / properties / evidence / properties / join_keys / items / properties / role / enum

Previous value: -[
-  "account_id",
-  "marketplace_id",
-  "asin",
-  "advertised_asin",
-  "purchased_asin",
-  "child_asin",
-  "parent_asin",
-  "seller_sku",
-  "fnsku",
-  "order_id",
-  "order_item_id",
-  "campaign_id",
-  "ad_group_id",
-  "ad_id",
-  "target_id",
-  "keyword_id",
-  "search_query",
-  "portfolio_id",
-  "shipment_id",
-  "inbound_plan_id",
-  "operation_id",
-  "transaction_id",
-  "settlement_id",
-  "promotion_id",
-  "not_applicable"
-]New value: +[
+  "account_id",
+  "marketplace_id",
+  "asin",
+  "advertised_asin",
+  "purchased_asin",
+  "child_asin",
+  "parent_asin",
+  "seller_sku",
+  "fnsku",
+  "order_id",
+  "order_item_id",
+  "campaign_id",
+  "ad_group_id",
+  "ad_id",
+  "target_id",
+  "keyword_id",
+  "search_query",
+  "portfolio_id",
+  "shipment_id",
+  "inbound_plan_id",
+  "operation_id",
+  "transaction_id",
+  "financial_event_group_id",
+  "settlement_id",
+  "promotion_id",
+  "not_applicable"
+]

changedOutput schema / properties / evidence / properties / metric_families / items / enum

Previous value: -[
-  "sales",
-  "traffic",
-  "advertising",
-  "inventory",
-  "returns",
-  "reimbursements",
-  "fees",
-  "profitability",
-  "catalog",
-  "rank",
-  "fulfillment",
-  "pricing",
-  "promotions",
-  "reviews",
-  "audit",
-  "availability",
-  "not_applicable"
-]New value: +[
+  "sales",
+  "traffic",
+  "advertising",
+  "inventory",
+  "returns",
+  "reimbursements",
+  "payouts",
+  "fees",
+  "profitability",
+  "catalog",
+  "rank",
+  "fulfillment",
+  "pricing",
+  "promotions",
+  "reviews",
+  "audit",
+  "availability",
+  "not_applicable"
+]

AddedOct 7, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotations, the description discloses the critical behavioral trait that this data lags the live Payments feed, that a date window can span multiple settlement IDs, and that transaction families may be missing from the V2 report. It further explains non-additive overlapping fee fields, excluded unattributed account-level fees, ASIN-resolution provenance, and a multi-currency caveat where amounts are not currency-filtered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the key sibling routing are front-loaded, but the body is a single dense block covering fee overlap, ASIN resolution, date fallbacks, and currency behavior with no headings or line breaks, making it hard to scan. Much of the summary-field enumeration is recoverable from the output schema, so several sentences do not fully earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter financial analysis tool with an output schema, the description covers the remaining gaps an agent needs: data latency, mode semantics, non-additive fields, unattributed fees, and the currency aggregation risk. An agent can call it correctly and interpret the results without further context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: detail mode gates amount_type/amount_description, settlement_effective_date is defined by a fallback chain (posted_date → posted_date_time → settlement_end_date → deposit_date → snapshot_date), and marketplace_currency is asserted from the scoped marketplace rather than read per row. The 366-day window constraint is only visible in the schema, and sort/pagination parameters get no treatment in the prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get settlement-report finalized financial data" gives a specific verb and resource, then immediately names the two modes (summary pivot by ASIN/SKU vs. raw detail rows). It also explicitly separates itself from get_payment_transactions for pre-finalization data, so an agent can distinguish it from the nearest sibling without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Routing guidance is explicit and repeated with conditions: use get_payment_transactions for recent refund/deferred/payment rows before settlement finalization, and use get_payment_transactions with financial_event_group_id + transaction_status=RELEASED for exact disbursement-group reconciliation. It also names get_financial_events for single-currency isolation, covering the when-not cases as well as the when.

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

All Agent Central tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.