Skip to main content
Glama

get_listing

Read-only

Retrieves full details for a Kleinanzeigen classified listing—description, price, condition, and seller—from a listing URL or ad ID.

Instructions

Full details of one listing: description, price, condition details, seller.

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

Input Schema

NameRequiredDescriptionDefault
listingYesListing URL or ad id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description adds genuinely new context by listing the returned fields — important since there is no output schema. It stops short of covering failure behavior (missing/removed listing) or any rate/access limits.

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?

One short sentence, front-loaded with the resource and followed by the payload fields, with no wasted wording. The telegraphic fragment style is slightly terse but appropriate for a simple lookup.

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 one-parameter read tool this covers the essentials: what it fetches, how it is identified via the schema, and what the response contains. Only error/not-found behavior and routing relative to search_listings are missing.

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 description coverage is 100% and the single parameter already documents 'Listing URL or ad id'. The phrase 'one listing' in the description only restates that, adding no format, ambiguity resolution (URL vs. id), or example value.

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?

The description names a specific resource ('one listing') and enumerates what comes back (description, price, condition details, seller), so an agent can tell this is a single-record detail fetch rather than a bulk operation like search_listings. It is a fragment with no explicit verb, and it never names the sibling it contrasts with, so it falls short of a 5.

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 only implied: 'one listing' suggests calling it after a search narrows to a specific ad. There is no explicit when-to-use statement, no exclusion such as 'use search_listings to find listings first', and no note about what happens with an invalid or expired id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.