Skip to main content
Glama

Nova Amazon MCP Server

import_supplier_orders

Destructive

DEPRECATED (2026-10-22): use import_supply_chain (orderUnits, expectedOn, reference and status per line, one line per order); this tool stays for callers that still use it. Import the SUPPLIER ORDERS of ONE account — the seller's purchase orders on ITS supplier (not Amazon Vendor POs), per product × stock region: the fifth rung of the ladder, what query_inventory returns as onOrderUnits / nextExpectedAt and counts in coverageTotal / recommendedOrderQty. Only OPEN lines count; 'received' and 'cancelled' are history. TWO-STEP like import_stock_params: preview WITHOUT commit (warnings + per-region diff + confirmationToken), show the user, then commit with the token. Mode 'merge' (default): a line WITH a reference updates the line of the same (product, region, reference) — re-send it with status 'received' when the goods land —, the lines WITHOUT a reference restate the OPEN unreferenced book of their (product, region) — re-sending them is safe, received / cancelled lines untouched; 'replace' restates the OPEN order book of every (account, region) present in rows (open lines absent from rows are deleted, history untouched) and accepts status 'open' only. Up to 2000 rows per call. Requires the OAuth connection and the OWNER role.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "rows": "<rows>"
    },
    "name": "import_supplier_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'merge' (default): a referenced line updates its namesake; the unreferenced lines of a (product, region) replace its open unreferenced ones. 'replace': restate the OPEN book of each (account, region) present in rows.
rowsYes
commitNoOmit/false = preview (validate + diff, no write). true = write; requires the confirmationToken from the preview.
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.
accountYesThe seller account (seller_partner_id, or an unambiguous account name). One account per call.
confirmationTokenNoThe token the preview returned — proves the user saw exactly this payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rows / items / properties / region / description
      Previous value: -"A stock region as get_stock_setup lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted). Never 'ALL': the units sit in one place."New value: +"A stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted). Never 'ALL': the units sit in one place."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them by specifying exactly what is deleted ('open lines absent from rows are deleted, history untouched'), what is safe to re-send, the 2000-row cap, the OAuth + OWNER role requirement, and the preview payload (warnings, per-region diff, confirmationToken). The only meaningful gap is output format after a successful commit, which is out of scope for a tool with no output schema.

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?

Front-loaded correctly with DEPRECATED, purpose, two-step, then mode semantics, and nearly every clause carries information. But it is a single dense paragraph that duplicates the schema's own mode and status explanations almost verbatim, and the em-dash clause chains make it harder to scan than it needs to be.

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 destructive, high-blast-radius import with 6 parameters, the description covers authorization, row limits, the preview/commit contract, and the exact delete semantics of replace mode. Nothing an agent needs before calling it safely is missing, and no output schema exists to explain away.

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 83%, so the baseline is already 3; the description adds real meaning on top by explaining how reference presence changes merge behavior and how omission of status behaves ('a received order is never re-opened by omission'). It largely restates the schema's own mode and status text, however, rather than adding new semantics for those two parameters.

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 ('Import the SUPPLIER ORDERS of ONE account'), immediately scopes what is NOT meant ('the seller's purchase orders on ITS supplier (not Amazon Vendor POs)'), and names the sibling replacement import_supply_chain. It also ties the resource to what query_inventory returns (onOrderUnits / nextExpectedAt), so an agent can place it precisely among siblings.

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?

Explicit deprecation with a date and a named alternative with its field names, plus a direct instruction to keep using this tool only for existing callers. It also gives the when/when-not for modes ('merge' default vs 'replace'), states the two-step preview-then-commit flow, and excludes closed history lines from counting.

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.