Skip to main content
Glama

Nova Amazon MCP Server

get_listing_content

Read-only

Seller Central only (a Vendor Central account is refused by name: its content is changed in Vendor Central). Read the CURRENT editable content of up to 20 SKUs as Amazon holds it: title, bullets, description, backend keywords, and every other attribute the product type schema marks editable, flattened by column (item_name, bullet_point[1..10], item_dimensions.length.value…). account is optional: without it the SKUs are located across your accounts (one match = read; several = the matches are listed for you to pick). marketplaces takes country codes (FR), domains (amazon.fr) or ids; omitted = every marketplace the SKUs are listed on, with the values shared by all of them returned once under common. Only filled values are returned; emptyEditableAttributes names what the listing lacks; readOnlyAttributes cannot be changed through the API (Amazon's locks, and Nova's own: the offer — price, stock, shipping, tax, condition, offer images — is never written by Nova). Values are read from Amazon at call time (one call per SKU, asOf = the read time). This is the 'before' you MUST show the user before proposing any change.

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": {
      "skus": "<skus>"
    },
    "name": "get_listing_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
skusYes
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.
accountNoThe seller account (seller_partner_id, or an unambiguous account name). Omit to locate the SKUs across your accounts.
marketplacesNoCountry codes (FR, DE), domains (amazon.fr) or marketplace ids. Omit for every marketplace the SKUs are listed on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare a safe read; the description adds substantive behavior: values are fetched from Amazon at call time (asOf = read time), one call per SKU, only filled values are returned, emptyEditableAttributes names gaps, readOnlyAttributes are immutable (Amazon locks plus Nova's own offer-data exclusion), and ambiguous account matches are surfaced for the user to pick. This is rich operational context the annotations cannot convey.

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-loads the most restrictive constraint (Seller Central only) and routes into scope, returns, and parameters in a logical order. It is a single dense paragraph with some run-on packing (backtick-laden parentheticals), but nearly every sentence carries operational value.

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, and the description compensates fully by describing the flattened column shape, the `common` section, and `emptyEditableAttributes`. Combined with the 20-SKU cap and per-SKU call model, an agent has everything needed to call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Goes well beyond the 75%-covered schema: for `account` it explains the cross-account resolution logic (one match = read, several = matches listed for the user to pick) and for `marketplaces` it spells out accepted formats and the `common` collapse when values are shared across all marketplaces. These are behavioral consequences of parameter choices, not restatements of the schema.

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 ('Read the CURRENT editable content of up to 20 SKUs') and enumerates exactly what is returned (title, bullets, description, backend keywords, every editable attribute of the product-type schema). It also draws a hard boundary against Vendor Central accounts, so an agent can tell immediately whether this tool applies.

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 explicit when-to-use guidance: 'This is the "before" you MUST show the user before proposing any change', plus a when-not condition (Vendor Central accounts are refused by name). It does not name the write-side alternative, but the usage context is unambiguous from the text itself.

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.