Skip to main content
Glama

Get listing details

get_item
Read-onlyIdempotent

Get the full public details of one listing: description, price in EUR, condition and quality grade, brand and designer, dimensions, materials, photos, seller reference and the whoppah.com link. Pass the id (or slug) from search_catalog. Every item is a one-off, so check it here before recommending a specific piece. Only listings that can be bought or bid on right now are returned. not_found means the item has sold, expired or been withdrawn, not that it never existed: offer the buyer alternatives (search_catalog, or similar_items on a comparable listing) instead of describing it.

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_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
slugNo
languageNoThe buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "en",
      +  "description": "The buyer's language: titles come back as whoppah.com shows them in it, and links open the listing's page in it.",
      +  "enum": [
      +    "en",
      +    "nl",
      +    "de",
      +    "fr",
      +    "es",
      +    "it"
      +  ],
      +  "title": "Language",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real operational context: only currently buyable/biddable listings are returned, and not_found means sold/expired/withdrawn rather than never existed. What it does not cover is the edge case created by the schema: both id and slug are optional, and the description never says what happens if neither is supplied or which one wins if both are given.

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?

Front-loaded with purpose, then sourcing, then the pre-recommendation check, then the failure semantics. No filler sentences; every clause either defines scope ('public', 'right now') or changes agent behavior on error.

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 an output schema present, the tool does not need to explain return values, and the crucial agent-facing detail (not_found handling) is covered thoroughly. The remaining gap is the zero-required-parameter contract, which is the one thing an agent could get wrong when calling it.

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 only 33%, with id and slug carrying bare titles of 'Id' and 'Slug'. The description partially compensates by stating both come from search_catalog, implying they are interchangeable listing identifiers, but it does not explain id vs slug precedence or the all-optional contract. The language parameter is already fully documented in the schema, so the description adds nothing there.

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?

Opens with a specific verb and resource ('Get the full public details of one listing') and then enumerates exactly what comes back: description, EUR price, condition/quality grade, brand/designer, dimensions, materials, photos, seller reference and link. This is clearly distinguishable from search_catalog and similar_items, which the description itself names.

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?

Explicitly routes the agent: take the id/slug from search_catalog, and check the item here before recommending a specific piece because every item is a one-off. It also gives a when-not/what-next rule for the failure case, pointing to search_catalog or similar_items when the listing is gone. That is both the trigger and the alternative.

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