Skip to main content
Glama

search_listings

Read-only

Search kleinanzeigen.de classified listings by query, page, and optional EUR price range, returning up to about 25 results with prices and negotiable status.

Instructions

Search kleinanzeigen.de. Returns up to ~25 listings per page with price and whether it is negotiable (VB).

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": {
      "query": "<query>"
    },
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryYes
max_price_eurNo
min_price_eurNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, but the description adds genuinely useful context: that results are paginated at roughly 25 per page and that each result includes price and a negotiable (VB) flag. Because there is no output schema, this return-value context is valuable. It says nothing about depth of results, rate limits, or authentication.

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, front-loaded with the action and resource, with zero filler. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, four-parameter search tool, the description covers what the tool is and what it returns but omits parameter semantics at 0% schema coverage and offers no routing guidance against sibling tools. The gaps are not severe, but the description should have done more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must supply meaning for the four parameters; it only alludes to paging with "per page." The price filters (min_price_eur and max_price_eur) and the query parameter's semantics are entirely undocumented here, so the agent has to guess what is accepted and how to filter.

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 verb ("Search") and a specific resource (kleinanzeigen.de listings), so the agent knows exactly what operation this performs. It does not, however, distinguish itself from candidate siblings such as get_listing, leaving the search-vs-fetch distinction implicit.

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: the description indicates that this searches listings and what the results contain (about 25 per page, price, and negotiable flag), which helps the agent decide when this tool fits. It gives no explicit guidance about when to use this tool instead of a listing-detail tool or which parameters to set to narrow the search.

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