Skip to main content
Glama

run_kleinanzeigen_sellers_listings

Retrieve active Kleinanzeigen listings for a seller by user ID or profile URL. Supports pagination and up to 500 records per request.

Instructions

A seller's active Kleinanzeigen ads by user id or profile URL. 1 point per returned record.

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": {
      "seller": "<seller>"
    },
    "name": "run_kleinanzeigen_sellers_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYesSeller user ID or profile URL. e.g. 4667542
max_itemsNoMax items (up to 500)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that only *active* ads are returned and that cost is 1 point per record, but says nothing about pagination behavior, ordering, or rate limits.

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 tight sentences with zero filler, the resource and keying options front-loaded, and the credit cost relegated to a trailing clause.

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 simple three-parameter list tool with a fully documented schema and no output schema, the description covers what is needed: what is returned (active ads), how it is keyed, and the cost. Missing only pagination/ordering hints, which the schema partly handles.

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%, so all three parameters are documented in the schema. The description confirms the seller parameter accepts either a user ID or a profile URL, adding marginal value; baseline 3 applies.

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?

Specific verb+resource: a seller's active Kleinanzeigen ads, keyed by user id or profile URL. It clearly targets a seller's listings rather than a general listing search, though it does not name the sibling (e.g., run_kleinanzeigen_sellers for profile data) it diverges from.

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 lets an agent infer this is the tool for 'all ads from one seller' but never states when to prefer it over run_kleinanzeigen_listings_search or run_kleinanzeigen_sellers, nor any prerequisites.

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

Deploy Server

Other Tools