webdata-tools-mcp

Search German property listings (ImmoScout24)

search_german_property_listings

Read-onlyIdempotent

Find apartments and houses for rent or sale in Germany by city, price, area, rooms, and type, returning structured listing data.

Instructions

Apartments and houses for rent or sale in Germany: price, rent, area, rooms, address with coordinates, energy class, features, agent, photos and dates. Germany only. Runs the Apify Actor tacps126/immobilienscout24-scraper on your Apify account (about $0.001 per listing; spend per call is capped at $0.5).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`min_area`	No	Minimum area in m2.
`locations`	Yes	Cities, districts or regions in plain words, e.g. ["Berlin","München Schwabing"].
`max_items`	No	Maximum results to return (default 50, max 500). Cost scales with this.
`max_price`	No	Maximum price in EUR (monthly rent or purchase price).
`min_price`	No	Minimum price in EUR (monthly rent or purchase price).
`min_rooms`	No	Minimum number of rooms.
`offer_type`	No	Rent or buy listings.	rent
`extra_input`	No	Advanced: extra Actor input fields, merged over the defaults.
`property_type`	No	Apartments or houses.	apartment

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	Name of the tool that produced the result.
`count`	Yes	Number of records the Actor returned.
`items`	Yes	The records. Long text fields are shortened to 600 characters.
`shown`	Yes	Number of records included in `items` (can be lower than count when the result is long).
`truncated`	Yes	True when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.1.1Oct 17, 2026

addedInput schema / properties / max_price / description

Added value: +"Maximum price in EUR (monthly rent or purchase price)."

addedInput schema / properties / min_price / description

Added value: +"Minimum price in EUR (monthly rent or purchase price)."

addedInput schema / properties / min_rooms / description
```
Added value: +"Minimum number of rooms."
```
addedInput schema / properties / offer_type / description
```
Added value: +"Rent or buy listings."
```
addedInput schema / properties / property_type / description
```
Added value: +"Apartments or houses."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Number of records the Actor returned.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records. Long text fields are shortened to 600 characters.",
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shown": {
+      "description": "Number of records included in `items` (can be lower than count when the result is long).",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "tool": {
+      "description": "Name of the tool that produced the result.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when records were left out to keep the result short; ask for fewer items.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "count",
+    "shown",
+    "truncated",
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real operational context annotations cannot: it runs a specific Apify Actor on the caller's account, costs roughly $0.001 per listing, and hard-caps spend at $0.5 per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences: result scope first, geographic constraint second, then billing/implementation. Every clause carries information and nothing is repeated, though the field enumeration is long and sits closer to an output summary than to purpose.

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 read-only search tool with a full output schema and complete parameter descriptions, the definition covers the remaining gaps an agent needs: geographic restriction and the monetary cost ceiling that governs whether it is safe to call with a large max_items.

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 all nine parameters (locations, price/area/room bounds, offer_type, property_type, max_items, extra_input) are already documented inline. The description adds no parameter syntax or format detail beyond what the schema provides; the cost note merely reinforces max_items, which the schema already flags.

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?

States the resource (apartments and houses for rent or sale), the geography (Germany only), and enumerates the returned fields (price, area, rooms, coordinates, energy class, agent, photos). No sibling tool overlaps this vertical, so an agent can route to it unambiguously.

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 the content (property search) and there is one exclusion ("Germany only"), but the description never states when to prefer this over alternatives or what a caller should do if listings are needed outside Germany. Adequate but no explicit routing guidance.

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

Deploy Server