kleinanzeigen-mcp

Find categories

find_category

Read-only

Resolve German category names to numeric category IDs. Provide a category name or 'Parent > Child' path to get matching candidates with unique IDs for accurate Kleinanzeigen searches.

Instructions

Category ids matching a name. Always returns candidates — names and slugs collide, so only the numeric id identifies a category.

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": "find_category"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A German category name, optionally qualified as "Parent > Child".

Output Schema

Name	Required	Description	Default
`count`	Yes
`stale`	Yes
`matches`	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

A4.1/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the readOnlyHint: it warns that matches always come back as candidates because names and slugs collide, and that only the numeric ID is authoritative. This is valuable context that prevents an agent from assuming a single, clean match.

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 tightly worded sentences: the first front-loads the core purpose, and the second adds only the essential caveat about collisions and ID authority. Every clause earns its place, with no fluff or repetition.

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

Completeness5/5

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

For a single-parameter read-only lookup tool with a full input schema, an output schema, and readOnlyHint annotation, the description covers the key operational caveat an agent needs. Nothing important is missing for correct invocation and interpretation.

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 query parameter is already well described as a German category name with optional parent qualification. The tool description adds general context about ambiguity but does not add new parameter-level details, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: finding category IDs by name. The follow-up sentence explains the result shape (candidates) and the unique identifier, distinguishing this from sibling find tools operating on locations and shops.

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?

The intended use is implied: call this tool when you have a category name and need the corresponding numeric category ID. However, it does not explicitly state when not to use it or name alternatives, so the guidance remains implicit rather than directive.

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

Deploy Server