Skip to main content
Glama

Get listing

get_listing
Read-onlyIdempotent

Full public details of one listing by id: description, price, condition, specs, delivery, seller type, photos and URL. Phone numbers and emails stay hidden (they are shown on the site after sign-in).

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
idYesListing id from search_listings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower, and the description still adds real context: phone numbers and emails are withheld and only visible on the site after sign-in. That prevents an agent from promising contact data it cannot return. It stops short of covering not-found or expired-listing behavior.

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 sentences, zero padding. The purpose and returned fields come first, and the privacy caveat is placed as a trailing qualifier where it belongs.

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 no output schema, the description usefully sketches the return shape (field list) and its limits (hidden contact info), which is enough to act on. Minor gap: nothing about error/empty behavior when an id is stale or the listing was removed.

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%: the single id parameter already carries a UUID pattern and a description pointing to search_listings. The phrase "by id" adds no format or sourcing detail beyond that, so this is the baseline case where the schema does the work.

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 ("Full public details of one listing by id") and enumerates the payload surface: description, price, condition, specs, delivery, seller type, photos, URL. The singular "one listing" plus the id requirement clearly separates it from search_listings, which returns many.

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 rather than stated: fetching details for a listing whose id you already hold. The id's provenance is only given in the schema ("Listing id from search_listings"), not the description, and there is no explicit when-not or named alternative for bulk/browse needs.

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