Skip to main content
Glama

Nova Amazon MCP Server

get_listing_change_status

Read-only

Seller Central only. Follow a listing change pushed from Nova: by batchId (the id update_listing_content returned) — every SKU with its Amazon status (SUBMITTED → ACCEPTED → STORED → PUBLISHED, or INVALID / REJECTED / NOT_REFLECTED / FAILED), its clocks (storedAt: Amazon holds the values; publishedAt: the public product page shows them, verified on the public catalogue; nextCheckAt: when Nova looks again, from 2 minutes to 72 hours after the change) and its issues, including why a stored value is not proven published (an attribute the public catalogue never shows, such as backend keywords, stays STORED with that reason) — or by marketplace + sku: the timeline of every attribute changed from Nova on that listing, with before/after, its status, its own publishedAt and its issues. It follows the changes sent through Nova only: an edit made in Seller Central is not listed, and a listing Nova never changed answers an empty changes with a note saying so.

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>"
    },
    "name": "get_listing_change_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
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).
batchIdNo
marketplaceNoA country code (FR), a domain (amazon.fr) or the marketplace id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld=false, but the description goes well past them: the full status lifecycle (SUBMITTED → ACCEPTED → STORED → PUBLISHED vs INVALID/REJECTED/NOT_REFLECTED/FAILED), the meaning of storedAt vs publishedAt, and the nextCheckAt polling window of 2 minutes to 72 hours. It also explains a non-obvious edge case — attributes the public catalogue never shows stay STORED with that reason — and what an empty result looks like.

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 scope constraint ('Seller Central only') and the core action before the detail. It is dense — one long em-dash sentence carrying the status list, clocks and issues — but every clause conveys operative information such as status values, timestamp meanings and the empty-result behavior.

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?

There is no output schema, so the description carries the return-shape burden and does: it enumerates statuses, explains each timestamp field, describes issues and the before/after attribute timeline, and notes the empty `changes` case. An agent can call and interpret results without further documentation.

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 60%, with sku and batchId left undescribed in the schema. The description compensates for batchId by tying it to the value update_listing_content returns, and pairs marketplace with sku, which the schema does not do. It adds no format detail for sku, so not a full 5.

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 ('Follow a listing change pushed from Nova') and immediately carves out the two lookup modes: batchId (the id update_listing_content returned) and marketplace + sku. It is distinguishable from get_listing_content and query_listing_health by being explicitly about tracked change status and per-attribute timelines.

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 conditions for each mode: use batchId when following a push from update_listing_content, use marketplace + sku for a per-attribute timeline on a listing. It also states a real exclusion — Seller Central edits are not listed, and a never-changed listing returns an empty `changes` with a note. It stops short of naming a sibling tool to use instead for that case, which keeps it from a 5.

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.