Skip to main content
Glama
Sign In
NeuralVerge

NeuralVerge

Official
by neuralverge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

run_kleinanzeigen_listings_similar

Fetch similar Kleinanzeigen ads by ad ID or URL to discover related listings and alternatives.

Instructions

Related ads Kleinanzeigen shows on an ad's page, by ad id or 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": {
      "ad": "<ad>"
    },
    "name": "run_kleinanzeigen_listings_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
adYesAd ID or URL. e.g. 3517031976
max_itemsNoMax items (up to 100)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add one genuinely useful behavioral fact — '1 point per returned record' cost — but says nothing about return shape, whether results are paginated, or how many related ads are typically available, which matters given there is no output schema.

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 resource and scope, with the cost note appended last. Nothing is wasted and there is no filler.

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 simple 3-parameter retrieval tool the description covers the source and the cost, which is the minimum viable set. But with no annotations and no output schema, it should say more about what a returned record contains or how pagination behaves.

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%, so the schema already documents ad, max_items, and start_page. The description's 'by ad id or URL' merely restates the schema's own parameter description, adding no new semantics. 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?

The description states a specific action and resource: related ads that Kleinanzeigen surfaces on an ad's page, keyed by ad id or URL. This clearly distinguishes it from the generic run_kleinanzeigen_listings_search, but it never names a sibling explicitly, so routing relies on the agent inferring the distinction.

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 implied by 'related ads Kleinanzeigen shows on an ad's page' — an agent can infer this is the recommendation/similar-ads lookup rather than a keyword search. However, there is no explicit when-to-use/when-not-to-use statement or named alternative (e.g. use listings_search for keyword discovery instead).

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