Skip to main content
Glama

Nova Amazon MCP Server

import_stock_params

Destructive

DEPRECATED (2026-10-22): use import_supply_chain, the Supply chain table as one line per product and warehouse, which changes only the lines it names; this tool stays for callers that still use it. Import the REORDER PARAMETERS of ONE account — per product × stock region (or 'ALL'): production lead time, transit lead time to Amazon, lead time from the factory to the warehouse (leadTimeToWarehouseDays), target days of cover at Amazon and at the external location, case pack. A product needs all five to RESOLVE (its own row → its 'ALL' row → the account defaults) before query_inventory recommends anything; a blank field resolves to the next rank, so set the account-wide values with set_stock_defaults and import here only the exceptions. A seller shipping straight from the factory to FBA has an external target of 0 and a to-warehouse lead time of 0, not blank. TWO-STEP, never skip the preview: call WITHOUT commit; the server validates (ASINs against the account's stocked products, regions, ranges) and returns per-row warnings, an ASIN-grain diff per (account, region) and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/mode/rows plus commit:true and the token. Mode 'merge' (default) touches only the (ASIN, region) rows you send, FIELD by field — a field you omit keeps its current value, null clears it; 'replace' restates every (account, region) present in rows whole — a product absent from rows loses its row there, an omitted field is blank. A row with nothing on it is refused (an import never clears a row). 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_stock_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'merge' (default): only the sent rows change. 'replace': restate 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) or 'ALL' (every region without its own row)."New value: +"A stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row)."
  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 flag a destructive, non-read-only write; the description adds real context beyond that — server-side validation against stocked ASINs/regions/ranges, per-row warnings, an ASIN-grain diff per account/region, the confirmationToken binding, the 2000-row cap, the refusal of empty rows, and the OAuth plus OWNER role requirement. The only thing not disclosed is what the write response payload looks like, which is minor given no output schema exists.

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?

The deprecation and the core purpose are correctly front-loaded, and every sentence carries information, but the body is a single dense block of run-on clauses (resolution ranks, two-step flow, merge/replace, limits, auth) with no structure. Splitting into short labelled sentences would cut reread cost without dropping content.

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, multi-row import with no output schema, the description covers everything an agent needs to call it safely: prerequisites, the preview/commit handshake, return artefacts, size limits, and the exact consequence of each mode on rows not named. There is no material gap left for the agent to guess at.

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 3; the description goes beyond it by explaining the resolution chain (own row → 'ALL' row → account defaults) that gives blank-vs-0 its meaning, and by spelling out field-by-field merge versus wholesale replace semantics. The 'a seller shipping straight from the factory to FBA has an external target of 0 and a to-warehouse lead time of 0, not blank' note is a genuinely non-obvious value rule that the schema does not convey.

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 with exact scope: 'Import the REORDER PARAMETERS of ONE account — per product × stock region (or ALL)', then enumerates the five fields involved. It also names the sibling that supersedes it (import_supply_chain) and the sibling that complements it (set_stock_defaults), so the 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?

Gives explicit routing: use import_supply_chain instead for new work, set the account-wide values with set_stock_defaults and import only exceptions here. It also prescribes the mandatory two-step flow (preview without commit, then commit with token after explicit user approval) and when to pick merge vs replace, so there is little left to infer.

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.