Skip to main content
Glama

Nova Amazon MCP Server

get_supply_chain_products

Read-only

The PRODUCT table of the Supply chain page ("Product overrides") as the page shows it (2026-10-22): one line per product × warehouse, the lines of the page's file, which import_supply_chain writes. Each line carries the account, the warehouse (its name as get_setup domain=supply_chain lists it, its region: the territory its count and orders are keyed on, its country), the ASIN with its name and SKU count, dailyUnitsSold (Daily units sold, summed over the territories the warehouse ships to), the count At warehouse / 3PL (warehouseUnits: 0 is a count, null = never counted; countedOn; countLocation 'own' or '3pl'), the OPEN supplier orders one by one (orders: reference, units, expectedOn, overdue = expected before today UTC, createdOn; import_supply_chain closes an order on its reference), On order (onOrderUnits, nextExpectedOn, overdueOrders) and numbers, the six numbers of the line (casePack, targetStockAtAmazonDays, targetStockAtWarehouseDays, transitToAmazonDays, transitToWarehouseDays, productionLeadTimeDays), each { value, source } by the page's rule: the product's own number ('product': its override, the page's black figure) → the warehouse's number saved in the Warehouse & 3PL setup ('warehouse': the page's grey inherited figure), or for the production lead time the account's ('account') → Nova's fleet default ('fleet default': read from the fleet's shipments, the page's gold figure) → null when nothing resolves (a case pack is the product's or nothing). On a line straight from the factory (warehouse.straightFromFactory, the page's « Straight from the factory ») there is no warehouse on the way: warehouseUnits is null, targetStockAtWarehouseDays and transitToWarehouseDays read { value: null, source: 'not applicable' } (the page's n/a; the recommendation reads them 0) and transitToAmazonDays is the whole trip, factory to sellable at Amazon. view reads the page's views: missing-count (no count at the warehouse; never a line straight from the factory), overdue-deliveries (an open order past its expected date), missing-lead-time (no production lead time typed on the product or on the account); counts gives the size of each view under the same search and filters. Use it to match a seller's file to the exact lines before import_supply_chain, and after, to verify. Paginate with limit/offset.

Input Schema

NameRequiredDescriptionDefault
skusNoOnly the products of these SKUs.
tagsNo"Your Filters" tag IDS from list_tags (manual custom tags or predefined segmentations, Brand included) — a tag NAME is rejected.
viewNoThe page's view: 'all' (default), 'missing-count' (no count at the warehouse), 'overdue-deliveries' (an open supplier order past its expected date), 'missing-lead-time' (no production lead time typed on the product or on the account).
asinsNoOnly these ASINs.
limitNo
offsetNoRow offset for pagination (default 0).
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.
searchNoASIN, SKU or product name substring (the page's search).
accountsNoRestrict to a subset of your own seller account IDs (from list_accounts). Omit to include all your accounts. A brand/account name is accepted and resolved to its id when it matches one of your accounts unambiguously; a label that carries the id ("Brand (A1B2C3D4E5F6G)") resolves to that id.
warehouseNoOne warehouse: its name as get_setup domain=supply_chain lists it ("UNIS, Buena Park", or "UNIS"), or a stock region ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) for the warehouse serving it. Omit for every warehouse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / warehouse / description
      Previous value: -"One warehouse: its name as get_supply_chain_setup lists it (\"UNIS, Buena Park\", or \"UNIS\"), or a stock region ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) for the warehouse serving it. Omit for every warehouse."New value: +"One warehouse: its name as get_setup domain=supply_chain lists it (\"UNIS, Buena Park\", or \"UNIS\"), or a stock region ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) for the warehouse serving it. Omit for every warehouse."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint, the description discloses a great deal: the six-number resolution chain (product → warehouse → account → fleet default → null), the straight-from-factory exception with null warehouseUnits and 'not applicable' sources, overdue defined as expected before today UTC, and that import_supply_chain closes orders by reference. These are exactly the non-obvious behaviors an agent would otherwise get wrong.

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?

It front-loads the identity of the resource correctly, but the bulk is one long run-on paragraph of field-by-field column semantics with parenthetical asides. Nearly every detail is substantive, yet the packing makes it hard to scan and would benefit from being split into purpose / fields / views / usage sections.

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 no output schema and only a readOnly annotation, the description carries the full burden of explaining the returned rows — and it does, covering accounts, warehouses, regions, ASIN/SKU counts, units, open orders and the numbers object with sources. An agent can reason about the payload without ever calling the tool.

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 90%, so the baseline is 3, but the description adds genuine meaning: view semantics (missing-count never applies to straight-from-factory lines), warehouse resolution and region aliases, and what 'counts' returns. It does, however, reference a `counts` capability that has no corresponding parameter in the schema, which is mildly confusing.

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 concrete verb+resource: reading the Product table of the Supply chain page, one line per product × warehouse, with a named producer (import_supply_chain) and a named consumer workflow. It is unambiguously distinguishable from siblings like get_stock_worksheet or query_inventory, though the sheer density of field-level detail buries the core statement.

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

Usage Guidelines4/5

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

Explicitly says to use it 'to match a seller's file to the exact lines before import_supply_chain, and after, to verify', which is a real when-to-use condition tied to a specific sibling. It also cross-references get_setup for warehouse naming and explains pagination, but offers no explicit exclusions for when another worksheet tool is the better choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.