Skip to main content
Glama

Listing details

get_listing
Read-onlyIdempotent

Get the full record of one listing found with search_listings. Returns everything in the search result plus the seller's description, color, material, minimum offer, the on-chain provenance record (fingerprint and what it does and does not prove), when it was listed, and how to buy it: the checkout url and the payment methods it accepts. Use this before pricing or buying a piece. Fails with a clear message if the id does not exist or the piece is no longer for sale.

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": {
      "id": "<id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"Listing id (the slug from search_listings)"New value: +"The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure')."
    • addedInput schema / properties / id / minLength
      Added value: +1
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond that: it discloses the failure mode ('fails with a clear message if the id does not exist or the piece is no longer for sale') and flags that the provenance record has limits ('what it does and does not prove').

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 core action and then enumerates the returned fields in a single dense paragraph. It is longer than typical but nearly every clause carries information; the enumeration of return fields is the only mildly padded section.

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, so the description must carry the return contract, and it does: it lists the inherited search fields plus description, color, material, minimum offer, provenance, listing time, checkout url, and accepted payment methods. Error behavior is also covered, leaving nothing an agent needs to call it correctly.

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% and the schema already documents that the id is a slug from search_listings results. The description reinforces the source of the id but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 ('Get the full record of one listing') and explicitly ties it to search_listings as the discovery counterpart, so an agent can distinguish it from the search sibling without opening either schema.

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 a clear usage condition ('Use this before pricing or buying a piece') and points to search_listings as the source of the id. It does not spell out when-not-to-use or name the pricing/purchase siblings explicitly, so it stops short of full routing guidance.

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