Agent Central

Suppressed listings

get_suppressed_listings

Read-only

Get suppressed/stranded listings: items that are in FBA inventory but not buyable. Returns source suppression facts enriched with current listing titles where available. Reimbursement placeholder SKUs are filtered by default; set include_synthetic_skus=true to include rows flagged with is_synthetic. This table refreshes daily. Daily snapshots do not establish current live buyability.

Input Schema

Name	Required	Description	Default
`sku`	No	Filter by SKU
`asin`	No	Filter by ASIN
`limit`	No	Max rows (1-1000, default 20).
`offset`	No	Pagination offset (0-100000, default 0). Use the returned pagination.next_offset to continue.
`ob_date`	No	Filter by observation date (YYYY-MM-DD). Defaults to the latest successful suppressed-listings sync, which can be empty.
`sort_by`	No	Column to sort by	sku
`sort_order`	No	Sort order	desc
`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.
`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.
`include_synthetic_skus`	No	Include reimbursement placeholder SKUs such as FBA...missing1. Defaults to false.

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

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description's job is to add operational context - and it does: the table refreshes daily, snapshots do not prove current buyability, and the default ob_date window 'can be empty.' The default exclusion of reimbursement placeholder SKUs is also disclosed. It stops short of describing rate limits or result-size behavior, but the schema covers response shaping.

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?

Four sentences, front-loaded with the definition, then return content, then the synthetic-SKU toggle, then the freshness caveat. Nearly every clause earns its place; the final caveat is slightly terse and would be stronger if it named the live-status alternative.

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?

With 10 optional parameters fully documented in the schema and an output schema present, the description needs only to cover behavioral caveats and defaults - daily refresh cadence, snapshot staleness, default synthetic-SKU filtering, and the empty-default-window risk. All four are present, so an agent can call this correctly without further information.

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 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema by explaining that filtered rows are flagged is_synthetic and giving a concrete example value (FBA...missing1), which clarifies why include_synthetic_skus exists. The ob_date sentence also adds the non-obvious fact that the default window can return nothing.

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?

The description gives a specific verb and resource and then defines the domain concept precisely: 'suppressed/stranded listings: items that are in FBA inventory but not buyable.' It also states what the rows contain ('source suppression facts enriched with current listing titles'). It does not name which sibling to use instead (e.g. get_buybox_status or get_fba_inventory), so the differentiation from a large sibling set is left implicit.

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?

Usage context is implied rather than stated: an agent can infer this is the tool for not-buyable FBA inventory, and the note that 'daily snapshots do not establish current live buyability' hints at a different tool for live status. However, no alternative is named and there is no explicit when-not-to-use guidance.

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.