kleinanzeigen-mcp

Get shop page and inventory

get_shop

Read-only

Fetch a commercial seller's shop profile and current listings from kleinanzeigen.de. Provide a shop slug to view ads, filterable by keyword, price, category, and location.

Instructions

Profile and listings for one COMMERCIAL seller. Private sellers have no shop page and cannot be reached by this server.

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": {
      "shop_slug": "<shop_slug>"
    },
    "name": "get_shop"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`keywords`	No
`max_price`	No
`min_price`	No
`shop_slug`	Yes
`category_id`	No
`location_id`	No

Output Schema

Name	Required	Description	Default
`page`	Yes
`shop`	Yes
`count`	Yes
`stale`	Yes
`status`	Yes
`listings`	Yes
`fetched_at`	Yes
`source_url`	Yes
`stale_reason`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by restricting the tool to commercial sellers, but it does not disclose behavior around pagination, filtering semantics, or what happens when a private or invalid shop_slug is provided.

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?

The description is two short sentences with no filler. The primary purpose and the key limitation are both front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Although annotations and an output schema reduce the burden, the description is too thin for a tool with 7 parameters and 0% schema coverage. It lacks parameter semantics, pagination/filtering context, and explicit routing to sibling tools, so an agent would still have to guess important invocation details.

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%, and the description does not compensate. It only hints that shop_slug refers to a commercial seller's shop. The meaning and combined behavior of page, keywords, max_price, min_price, category_id, and location_id are left entirely unexplained, which is a significant gap for a tool with 7 parameters.

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?

The description clearly states the resource and scope: 'Profile and listings for one COMMERCIAL seller.' It distinguishes the tool from siblings by explicitly noting that private sellers have no shop page, so an agent can tell this is for a specific commercial shop rather than search listings or find shops.

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?

The description implies when to use the tool: when a specific commercial seller's shop and inventory are needed. It also gives a clear exclusion: private sellers are not reachable. However, it does not explicitly name sibling alternatives such as find_shop or search_listings, so the routing guidance is not fully explicit.

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

Deploy Server