Skip to main content
Glama

update_item_highlights

Destructive

Update Item Highlights on a listing. L'attributo UFFICIALE è title_differentiation (max 125 char, rollout titoli modulari 27/7/2026); item_highlights è il nome legacy visto su alcuni schema US — il tool risolve da solo quale espone lo schema del product type e scrive su quello. ATTENZIONE: non tutti i marketplace/product type lo espongono — dove manca il tool rifiuta con esito chiaro (not_supported) rimandando ai bullet_point (update_listing → bullet_point). VINCOLO Amazon: title_differentiation è accettato SOLO se il titolo (item_name) è ≤ 75 char — con un titolo più lungo il tool si ferma (title_over_limit): prima accorcia il titolo, poi scrivi gli highlights. Chiama senza confirm per il dry-run (VALIDATION_PREVIEW), confirm=true per scrivere.

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

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
confirmNotrue to apply after reviewing the dry-run
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.
highlightsYesArray of highlight strings (frasi brevi separate, totale ≤ 125 char)
product_typeNoAmazon product type — auto-detected if omitted

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. First observed

TDQS

A4.7/5.0
Behavior5/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 the operationally critical behavior: calling without confirm yields VALIDATION_PREVIEW and no write, confirm=true actually writes, and specific named failure outcomes (not_supported, title_over_limit) are enumerated. This is context an agent cannot get from the annotations.

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?

Dense and front-loaded: purpose first, then naming resolution, then constraints and failure modes, then the confirm workflow. Every sentence carries information, though the mixed Italian/English and stacked parentheticals (dates, rollout notes) add some parsing overhead.

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?

For a destructive, open-world mutation with no output schema, the description covers the confirm flow, fallback path, and two named error outcomes. It does not address permissions/account scope or whether changes are reversible, leaving minor gaps.

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 100%, so baseline would be 3; the description adds real meaning by explaining that confirm drives dry-run vs write and that product_type is auto-detected from the product type schema when omitted. The highlights 125-char cap and SKU semantics are only restated from the schema, so it does not fully exceed the structured fields.

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 ('Update Item Highlights on a listing') and immediately resolves the naming ambiguity between the official attribute title_differentiation and the legacy item_highlights, noting the tool auto-selects whichever the product type exposes. An agent knows exactly what the call mutates and why two names exist.

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 when-to-use and when-not-to-use: where the attribute is missing the tool returns not_supported and the agent should fall back to bullet_point via update_listing. It also states the hard prerequisite (item_name ≤ 75 chars, otherwise title_over_limit) and the ordering ('prima accorcia il titolo, poi scrivi gli highlights'), plus the dry-run-then-confirm workflow.

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