Skip to main content
Glama

Nova Amazon MCP Server

import_fbm_costs

Destructive

Import PER-PRODUCT FBM cost overrides for ONE account: the exceptions to the rate book (a product that ships at its own cost to a zone). A row's zone is a delivery country ('DE') or 'ROW'; the override wins over the seller's zone rate for that destination. A row's rule says what its cost multiplies ('per_unit', 'per_parcel'); without one it follows the zone rate's rule. TWO-STEP like import_cogs: preview WITHOUT commit (warnings + SKU-grain diff + confirmationToken), show the user, then commit with the token. Mode 'merge' (default) upserts only the (asin, sku, zone, period) keys you send; 'replace' wipes and restates every (account, zone) present in rows, destructive with a partial payload. 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_fbm_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'merge' (default): only the sent keys change. 'replace': wipe + restate each (account, zone) present in rows.
rowsYes
zoneNoDefault zone for rows that do not carry their own: a delivery country ('DE', 'GB') or 'ROW'.
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. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond them by naming exactly where the destruction lies: 'replace' wipes and restates every (account, zone) present in rows and is dangerous with a partial payload. It also discloses the 2000-row cap, the two-step token proof-of-preview, and the auth/role requirements.

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?

Front-loaded with the subject and the critical two-step warning early; dense but every clause carries information. It is long and packed into few sentences, which makes it slightly harder to scan than a bulleted structure would.

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, batched, two-step mutation with no output schema, the description covers what the preview returns (warnings, SKU-grain diff, confirmationToken), the row cap, and the commit path. Nothing an agent needs to call this correctly is missing.

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 coverage is 86%, so the nested row fields, enum values and fallback behaviour are already documented in the schema. The description reinforces the zone vocabulary ('DE' or 'ROW') and the rule multiplier semantics, but adds little the schema does not already say; 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?

"Import PER-PRODUCT FBM cost overrides for ONE account" states a specific verb, resource and scope, and immediately positions itself against the sibling rate-book tool by calling these "the exceptions to the rate book". An agent can distinguish this from import_fbm_zone_rates without opening either schema.

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?

Gives clear operating context: preview without commit, show the user, then commit with the token, plus the OAuth-connection and OWNER-role prerequisites. It implies the boundary with import_fbm_zone_rates via "exceptions to the rate book" but never states the routing rule explicitly ("use that tool for zone baseline rates").

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.