Agent Central

Placement breakdown

get_placement_breakdown

Read-only

Returns Sponsored Products performance by ad placement (Top of Search, Detail Page, Other, Off Amazon) within campaigns; recent ~3 days may be incomplete. Use to compare placement-level spend, sales, ACOS, ROAS, CTR, and CVR. Does not include campaign totals, keyword performance, or organic traffic; use get_campaign_performance/get_keyword_performance/get_sales_and_traffic.

Input Schema

Name	Required	Description	Default
`limit`	No	Max rows (1-1000, default 20).
`offset`	No	Pagination offset (0-100000, default 0). Use the returned pagination.next_offset to continue.
`sort_by`	No	Column to sort by	spend
`end_date`	No	Optional. YYYY-MM-DD. Defaults to today if omitted.
`profile_id`	No	Filter by profile ID
`sort_order`	No	Sort order	desc
`start_date`	No	Optional. YYYY-MM-DD. Defaults to 30 days ago if omitted.
`campaign_name`	No	Filter by campaign name (LIKE match, use % for wildcards)
`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.

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

A4.4/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, so safety is settled; the description adds the non-obvious data-freshness caveat that the recent ~3 days may be incomplete, which materially affects how an agent interprets near-today results. It stops short of describing pagination behavior or how diagnostics flags affect the payload, so it is strong rather than exhaustive.

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

Conciseness5/5

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

Three sentences, front-loaded with what is returned and the freshness caveat before the use case and the exclusions. No filler and no restatement of the title; each sentence carries distinct information.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers scope, freshness, metrics, and sibling routing for a read-only report tool. The one remaining ambiguity is the row granularity (daily vs. aggregated per campaign-placement), which the agent must infer from the campaign_name filter and pagination fields.

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 description coverage is 100% across all 10 parameters, so defaults, ranges, date formats, LIKE-wildcard filtering, and the diagnostics toggles are already documented. The description's listing of metrics and placements loosely maps to the sort_by enum and row content but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns Sponsored Products performance by ad placement') and enumerates the exact placement values (Top of Search, Detail Page, Other, Off Amazon) plus the campaign-level grain. It also explicitly names the sibling tools it is not (get_campaign_performance, get_keyword_performance, get_sales_and_traffic), so an agent can distinguish it without opening a 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?

Gives an affirmative use case ('compare placement-level spend, sales, ACOS, ROAS, CTR, and CVR') and two explicit exclusions with routing ('does not include campaign totals, keyword performance, or organic traffic; use ...'). Both when-to-use and when-not-to-use are covered with named alternatives.

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.