Skip to main content
Glama

get_listing_issues

Read-only

READ-ONLY. Issue Amazon di SKU SPECIFICI (una chiamata SP-API per SKU): usalo quando l'utente nomina 1-20 SKU. Per la domanda "quali dei miei articoli NON sono in vendita / sono bloccati / soppressi e perché" NON usare questo in loop: usa list_inactive_listings, che copre tutto il catalogo con una chiamata ogni 20 SKU.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_listing_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
skusNoElenco di SKU del venditore (array di stringhe).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
issue_localeNoLingua dei messaggi di errore Amazon, es. it_IT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / issue_locale / description
      Added value: +"Lingua dei messaggi di errore Amazon, es. it_IT."
    • addedInput schema / properties / skus / description
      Added value: +"Elenco di SKU del venditore (array di stringhe)."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the 'READ-ONLY' prefix is largely redundant. The real added value is the cost model: one API call per SKU, which warns against looping and explains why the bulk sibling exists. It does not describe what the response contains (per-SKU error text, severity), which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the read-only status and the one-line definition, then the positive trigger, then the anti-pattern with the redirect. No filler and the emphasis on 'NON' carries the routing signal efficiently.

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 simple three-parameter read tool with full schema coverage and safety annotations, the definition covers purpose, scope, batching economics, and the sibling redirect. The one thing not covered is what the returned issues look like, and since no output schema exists the agent must infer the shape of the result.

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 all three parameters are already documented, giving a baseline of 3. The description adds genuine meaning beyond the schema by bounding the useful `skus` array to 1-20 entries, a practical constraint the schema does not state. The `account_id` and `issue_locale` parameters receive no elaboration in the description.

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 description names a specific verb+resource ('Issue Amazon di SKU SPECIFICI') and adds the crucial scope detail that it is one SP-API call per SKU. It distinguishes itself from the sibling list_inactive_listings by name and by the drastically different call-per-SKU vs. call-per-20-SKUs cost model.

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 ('usalo quando l'utente nomina 1-20 SKU') and explicit when-not-to-use, with the correct alternative named for the catalog-wide 'which items are blocked/suppressed and why' question. The exclusion is framed in terms of the user's actual question, not just a tool name.

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