Agent Central

Payment transactions

get_payment_transactions

Read-only

Get live Amazon Payments transactions (default), payout groups (view=payouts), current/historical balance trees (view=balances), or date/settlement net proceeds and breakdowns (view=financial_summary). Balance and financial_summary views return one complete, marketplace-scoped page with source currencies and timestamps; nested amounts overlap and are not additive. Payouts are seller-account groups in the connection region. Transaction detail preserves signed breakdowns; financial_event_group_id with transaction_status=RELEASED returns a payout's transaction pages. Amazon's payout transaction feed includes one Transfer line per payout carrying the prior payout amount. This carry-forward is not part of the current payout total: the RELEASED transaction total excluding Transfer corresponds to that payout's OriginalTotal. Transfer rows remain included in this response. Returns source facts, not seller actions.

Input Schema

Name	Required	Description	Default
`view`	No	transactions = existing summary/detail; payouts = regional seller-account groups; balances = current or as_of_date balance tree; financial_summary = dated or settlement net proceeds. New overview views return one complete upstream page, not a limit-sized slice.	transactions
`limit`	No	Maximum matching transactions in date/order modes (1-500). Payouts request min(limit, 100) groups. Group transactions, balances and financial_summary return a complete upstream page regardless of limit; continue with page_token.
`detail`	No	For view=transactions: true = transaction rows with source-signed nested breakdowns and separate non-additive item_breakdowns; false = grouped summary by date, transaction type, status, and currency. Payout rows are independent of detail.
`sort_by`	No	Transaction column to sort by after fetching: posted_date, total_amount, transaction_type, or transaction_status. Payouts retain Amazon's page order.	posted_date
`end_date`	No	Optional. YYYY-MM-DD end date for transaction postedDate, payout group start, or financial_summary period. The range may span at most 180 days. Defaults to today; only transactions/payouts apply the three-minute safety margin. Not valid for balances.
`order_id`	No	Optional Amazon order ID. Mutually exclusive with financial_event_group_id. Uses Amazon's ORDER_ID filter instead of postedAfter/postedBefore.
`as_of_date`	No	For view=balances only: historical YYYY-MM-DD balance date. Omit for current balances. Cannot be combined with start_date/end_date.
`page_token`	No	Opaque Amazon continuation token from pagination.next_token. Continue until pagination.has_more is false before treating a financial-event-group result as complete.
`sort_order`	No	Transaction sort direction after fetching. Payouts retain Amazon's page order.	desc
`start_date`	No	Optional. YYYY-MM-DD start date for transaction postedDate, payout group start (both UTC), or financial_summary period (marketplace calendar). The range may span at most 180 days. Defaults to 30 days ago. Not valid for balances.
`account_type`	No	For balances/financial_summary: exact Amazon account type, e.g. STANDARD_ORDERS. Omit for all account types within the key's marketplace.
`balance_type`	No	For view=balances only: Amazon balance category. Omit for all categories; TOTAL and RESERVED overlap their children.
`settlement_id`	No	For financial_summary: exact Amazon SETTLEMENT_ID, mutually exclusive with dates. History-limited plans require a dated summary instead.
`marketplace_id`	No	Optional assertion matching the tenant's selected marketplace_id after trimming. Transactions query that marketplace; payouts are seller-account groups in the connection's region because Finances v0 has no marketplace filter.
`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.
`transaction_type`	No	Optional exact transactionType filter applied locally (for example Refund, Shipment, ServiceFee, FBAInventoryReimbursement).
`transaction_status`	No	Optional Amazon transaction status filter: DEFERRED, RELEASED, or DEFERRED_RELEASED.
`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.
`financial_event_group_id`	No	Optional Amazon financial event group ID for exact payment/disbursement grouping. Mutually exclusive with order_id. Uses Amazon's FINANCIAL_EVENT_GROUP_ID filter instead of postedAfter/postedBefore; use transaction_status=RELEASED for finalized reconciliation.

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"
+  }
+]

Changed9 schema fields changedOct 28, 2026

addedInput schema / properties / account_type

Added value: +{
+  "description": "For balances/financial_summary: exact Amazon account type, e.g. STANDARD_ORDERS. Omit for all account types within the key's marketplace.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / as_of_date

Added value: +{
+  "description": "For view=balances only: historical YYYY-MM-DD balance date. Omit for current balances. Cannot be combined with start_date/end_date.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / balance_type

Added value: +{
+  "description": "For view=balances only: Amazon balance category. Omit for all categories; TOTAL and RESERVED overlap their children.",
+  "enum": [
+    "AVAILABLE",
+    "RESERVED",
+    "TOTAL",
+    "DEFERRED",
+    "ACCOUNT_LEVEL_RESERVE"
+  ],
+  "type": "string"
+}

changedInput schema / properties / end_date / description

Previous value: -"Optional. YYYY-MM-DD UTC end date for postedDate or payout group start. The range may span at most 180 days. Defaults to today when neither related identifier is supplied; the end timestamp is capped with a three-minute safety margin for Amazon's requirement."New value: +"Optional. YYYY-MM-DD end date for transaction postedDate, payout group start, or financial_summary period. The range may span at most 180 days. Defaults to today; only transactions/payouts apply the three-minute safety margin. Not valid for balances."

changedInput schema / properties / limit / description

Previous value: -"Maximum matching transactions in date/order modes (1-500). Financial-event-group transactions return one complete upstream page. Payouts request min(limit, 100) groups per page. Both group modes use page_token for continuation."New value: +"Maximum matching transactions in date/order modes (1-500). Payouts request min(limit, 100) groups. Group transactions, balances and financial_summary return a complete upstream page regardless of limit; continue with page_token."

addedInput schema / properties / settlement_id

Added value: +{
+  "description": "For financial_summary: exact Amazon SETTLEMENT_ID, mutually exclusive with dates. History-limited plans require a dated summary instead.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / start_date / description

Previous value: -"Optional. YYYY-MM-DD UTC start date for postedDate (transactions) or financial event group start (payouts). The range may span at most 180 days. Defaults to 30 days ago when neither related identifier is supplied."New value: +"Optional. YYYY-MM-DD start date for transaction postedDate, payout group start (both UTC), or financial_summary period (marketplace calendar). The range may span at most 180 days. Defaults to 30 days ago. Not valid for balances."

changedInput schema / properties / view / description

Previous value: -"transactions = existing transaction summary/detail; payouts = Finances v0 payout groups by group start date, in Amazon's page order. Payouts do not accept transaction filters or related identifiers."New value: +"transactions = existing summary/detail; payouts = regional seller-account groups; balances = current or as_of_date balance tree; financial_summary = dated or settlement net proceeds. New overview views return one complete upstream page, not a limit-sized slice."

changedInput schema / properties / view / enum

Previous value: -[
-  "transactions",
-  "payouts"
-]New value: +[
+  "transactions",
+  "payouts",
+  "balances",
+  "financial_summary"
+]

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / end_date / description

Previous value: -"Optional. YYYY-MM-DD UTC end date for postedDate or payout group start. Defaults to today when neither related identifier is supplied; the end timestamp is capped with a three-minute safety margin for Amazon's requirement."New value: +"Optional. YYYY-MM-DD UTC end date for postedDate or payout group start. The range may span at most 180 days. Defaults to today when neither related identifier is supplied; the end timestamp is capped with a three-minute safety margin for Amazon's requirement."

changedInput schema / properties / start_date / description

Previous value: -"Optional. YYYY-MM-DD UTC start date for postedDate (transactions) or financial event group start (payouts). Defaults to 30 days ago when neither related identifier is supplied."New value: +"Optional. YYYY-MM-DD UTC start date for postedDate (transactions) or financial event group start (payouts). The range may span at most 180 days. Defaults to 30 days ago when neither related identifier is supplied."

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."

Changed13 schema fields changedOct 27, 2026

changedInput schema / properties / detail / description

Previous value: -"true = transaction rows; false = grouped summary by date, transaction type, status, and currency."New value: +"For view=transactions: true = transaction rows with source-signed nested breakdowns and separate non-additive item_breakdowns; false = grouped summary by date, transaction type, status, and currency. Payout rows are independent of detail."

changedInput schema / properties / end_date / description

Previous value: -"Optional. YYYY-MM-DD end date for postedDate. Defaults to today when neither related identifier is supplied; postedBefore is capped with a three-minute safety margin for Amazon's requirement."New value: +"Optional. YYYY-MM-DD UTC end date for postedDate or payout group start. Defaults to today when neither related identifier is supplied; the end timestamp is capped with a three-minute safety margin for Amazon's requirement."

changedInput schema / properties / limit / description

Previous value: -"Maximum matching transactions in date/order modes (1-500). Financial-event-group mode returns one complete upstream page and uses page_token for continuation."New value: +"Maximum matching transactions in date/order modes (1-500). Financial-event-group transactions return one complete upstream page. Payouts request min(limit, 100) groups per page. Both group modes use page_token for continuation."

changedInput schema / properties / marketplace_id / description

Previous value: -"Optional marketplace ID assertion. If supplied, it must match the tenant's selected marketplace_id after trimming; the tool always queries the tenant marketplace."New value: +"Optional assertion matching the tenant's selected marketplace_id after trimming. Transactions query that marketplace; payouts are seller-account groups in the connection's region because Finances v0 has no marketplace filter."

changedInput schema / properties / sort_by / description

Previous value: -"Column to sort by after fetching: posted_date, total_amount, transaction_type, or transaction_status."New value: +"Transaction column to sort by after fetching: posted_date, total_amount, transaction_type, or transaction_status. Payouts retain Amazon's page order."

changedInput schema / properties / sort_order / description

Previous value: -"Sort direction after fetching."New value: +"Transaction sort direction after fetching. Payouts retain Amazon's page order."

changedInput schema / properties / start_date / description

Previous value: -"Optional. YYYY-MM-DD start date for postedDate. Defaults to 30 days ago when neither related identifier is supplied."New value: +"Optional. YYYY-MM-DD UTC start date for postedDate (transactions) or financial event group start (payouts). Defaults to 30 days ago when neither related identifier is supplied."

addedInput schema / properties / view

Added value: +{
+  "default": "transactions",
+  "description": "transactions = existing transaction summary/detail; payouts = Finances v0 payout groups by group start date, in Amazon's page order. Payouts do not accept transaction filters or related identifiers.",
+  "enum": [
+    "transactions",
+    "payouts"
+  ],
+  "type": "string"
+}

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still adds substantive context: balances/financial_summary return one complete marketplace-scoped page, nested amounts overlap and are not additive, payouts are scoped to the connection region because Finances v0 has no marketplace filter, and Transfer carry-forward rows are included but excluded from the payout OriginalTotal. These are non-obvious data-model caveats that prevent misreading results. What remains unstated is output/pagination limits and any rate considerations, but the core behavioral picture is strong.

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

Conciseness4/5

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

Front-loaded with the view enumeration, which is the primary dispatch decision, and every subsequent sentence adds a distinct caveat. It is dense but justified for a 19-parameter, four-mode tool. Some of the payout carry-forward explanation is verbose enough to slow scanning and could be tightened.

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

Completeness4/5

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

An output schema exists, so the description does not need to enumerate return fields, and it wisely spends its space on the non-additivity and Transfer carry-forward gotchas that a schema cannot convey. Given the tool's complexity, most of what an agent needs is present. The gap is relational context: no guidance on when to use this versus get_financial_events or get_settlement_economics.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all 19 parameters, and the description largely restates the view-mode split and the RELEASED/Transfer interaction rather than adding new parameter-level meaning. The margin-related notes (overlap, non-additivity, source currencies, timestamps) are primarily about result interpretation, not parameter semantics. Baseline 3 is appropriate; the extra context edges it upward but does not clearly reach 4.

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

Purpose4/5

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

States a specific verb and resource ("Get live Amazon Payments transactions") and enumerates the four modes it serves via the view parameter, so an agent knows the scope without opening the schema. It does not, however, distinguish itself from overlapping siblings such as get_financial_events or get_settlement_economics, which an agent selecting among these tools would need.

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

Usage Guidelines3/5

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

It gives clear in-tool routing guidance (default transactions, view=payouts for seller-account groups, view=balances, view=financial_summary) and one concrete usage rule (financial_event_group_id with transaction_status=RELEASED for finalized reconciliation). It stops short of saying when to choose this tool over sibling financial tools, and states no explicit exclusions beyond mode validity.

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.

Payment transactions

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources