Skip to main content
Glama

update_listing

Destructive

Modifica una listing esistente. Se scrive un prezzo (purchasable_offer) vale il limite ±50% sull'ultimo prezzo noto, come update_price. SHORTCUT amichevoli (consigliati — costruiscono la struttura attributo corretta, niente schema SP-API a mano): bullets:[...] → bullet_point ("Funzionalità principali", la leva dei punti-elenco su amazon.it/EU, fino a 5 ~100 char l'uno), title → item_name, shipping_template → merchant_shipping_group (modello di spedizione: ID o nome esatto come in Seller Central; il tool risolve il nome nell'ID e rifiuta i nomi sconosciuti elencando i modelli veri; vale per le offerte FBM). In alternativa patches:[...] grezzi (JSON Patch SP-API, path /attributes/; la struttura dell'attributo si legge con get_product_types attributes=[""]). Il productType del PATCH viene preso dalla listing (GET productTypes) quando product_type non è passato: 'PRODUCT' resta solo come ultima spiaggia e con il suo schema generico ogni attributo specifico (care_instructions, style, …) dà issue 90000900. L'esito riporta product_type_used e product_type_source (arg | listing | fallback_*). validate_only:true = dry-run (Amazon valida senza applicare). ESITO: ok true/false + message già leggibile + verify_with (= get_listing sullo SKU dopo ~15 min; propagazione tipica <30 min, fino a 24 h). Il submissionId NON è un feed: non passarlo a check_feed_status. ok:false con issues[] severity ERROR = rifiutata da Amazon, correggi e riprova (prima con validate_only).

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": {
      "sku": "<sku>"
    },
    "name": "update_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
titleNoNuovo titolo (item_name)
bulletsNoPunti elenco (bullet_point), fino a 5
patchesNoJSON Patch SP-API grezzi (alternativa agli shortcut)
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.
product_typeNoProduct type Amazon (es. WINDOW_SHADE). Opzionale: se manca si legge dalla listing; passalo solo per forzarlo
validate_onlyNotrue = dry-run, valida senza scrivere
shipping_templateNoModello di spedizione da assegnare (ID o nome come in Seller Central). Elenco: get_product_types product_type="PRODUCT" → shipping_templates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. Changed1 schema field changed
    • addedInput schema / properties / product_type / description
      Added value: +"Product type Amazon (es. WINDOW_SHADE). Opzionale: se manca si legge dalla listing; passalo solo per forzarlo"
  3. Changed1 schema field changed
    • addedInput schema / properties / shipping_template
      Added value: +{
      +  "description": "Modello di spedizione da assegnare (ID o nome come in Seller Central). Elenco: get_product_types product_type=\"PRODUCT\" → shipping_templates",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds real behavior: the ±50% price bound, validate_only as a true dry run, the product_type fallback chain with product_type_used/product_type_source reporting, the 90000900 failure mode for generic schemas, and the ~15min–24h verification window. The notable gap is that the two-step preview/confirm_id flow is never mentioned, even though the schema implies a confirm token is needed to actually write.

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 mutation and its price constraint, then the shortcut mappings, then the outcome contract — a sensible order for an agent. It is dense with parenthetical asides ("la leva dei punti-elenco su amazon.it/EU") that add flavor rather than decision value, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly documents the return shape (ok, message, verify_with, issues[] severity ERROR) and the propagation timing. It falls short only on the preview/confirm_id execution path, which for a destructive 9-parameter write tool is the one interaction an agent most needs spelled out.

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 100%, so the baseline is 3. The description does add genuine meaning over the schema for bullets (max 5, ~100 chars, maps to bullet_point) and for shipping_template (name-or-ID resolution, rejection of unknown names, FBM-only scope), but it says nothing about account_id or confirm_id, so it does not fully cover the write-gating semantics.

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?

The first sentence names the verb and resource ("Modifica una listing esistente") and the rest of the text immediately separates this tool from update_price (price cap behavior), from manual schema work via get_product_types, and from check_feed_status (submissionId is not a feed). An agent can place it among the update_* siblings without opening the schema.

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 routing guidance: recommended 'shortcut' parameters vs. raw patches, when to use each, the recommendation to retry with validate_only first after a rejection, and the explicit warning not to pass submissionId to check_feed_status. It also states that get_product_types attributes=[...] should be consulted before writing raw patches.

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.

Resources