Skip to main content
Glama

get_listing

Read-only

Fetch one listing (summaries, issues, offers, fulfillment availability). Pass include_data:["attributes"] for the full attribute set.

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": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
include_dataNoSezioni da includere nella risposta (array o elenco separato da virgole, es. issues,attributes,offers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / include_data / description
      Added value: +"Sezioni da includere nella risposta (array o elenco separato da virgole, es. issues,attributes,offers)."
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. First observed

TDQS

A3.7/5.0
Behavior3/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 safety profile is covered. The description adds real value by disclosing the default response sections and how to widen them, but it says nothing about behavior on an unknown SKU or about how account_id resolution failures surface.

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?

Two short sentences, the primary capability is front-loaded, and the parameter hint follows it. No filler, no restatement of the name or title.

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 three-parameter read tool with no output schema, the description covers what the tool returns by default and how to request more, which is the essential missing piece. Minor gaps remain around error/not-found behavior and the default of include_data, but nothing an agent needs in order to invoke it correctly is absent.

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 the baseline is 3, but the description adds meaning the schema does not: it gives a concrete call pattern for include_data (["attributes"]) and states that this yields the full attribute set rather than a subset. That clarifies the semantics of a free-form array parameter whose valid values are otherwise only loosely exemplified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch one listing") and enumerates the sections returned by default (summaries, issues, offers, fulfillment availability), which goes beyond the bare name. It stops short of explicitly distinguishing itself from siblings like get_listing_issues or get_my_catalog_detail, so an agent must still infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the required sku and the "fetch one listing" framing, and the include_data sentence gives a concrete condition for expanding the payload. However, there is no explicit when-to-use vs. when-not guidance and no reference to any alternative tool for issue-only or catalog-detail lookups.

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