Skip to main content
Glama

willhaben_search_real_estate

Search real estate listings for apartments, houses, or land on the Austrian classifieds marketplace. Filter by property type, price, rooms, area, and location.

Instructions

Search willhaben.at real estate listings (apartments, houses for sale/rent). Filter by property type, price, rooms, area, and location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_typeNoProperty type: 'eigentumswohnung' (apartment), 'haus' (house), 'mietwohnung' (rental), 'grundstueck' (land)
actionNoBuy or rent (default: buy)
locationNoLocation: Austrian state, city, place, or postal code (e.g. 'Wien', 'Graz', '6020'). Resolved to an area automatically.
price_fromNoMinimum price
price_toNoMaximum price
roomsNoNumber of rooms
area_fromNoMinimum living area in m²
area_toNoMaximum living area in m²
sortNoSort: 'newest', 'nearby', 'price_asc', 'price_desc', 'area_asc', 'area_desc', 'relevance'
rowsNoResults per page (default: 30)
pageNoPage number (default: 1)
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It only states the tool searches, with no disclosure of read-only nature, side effects, authentication needs, or rate limits. Minimal behavioral context.

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?

One concise sentence that front-loads the action and resource, followed by filter details. No extraneous words, and the structure is efficient.

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?

Given 11 parameters, no output schema, and no annotations, the description is minimal. It covers the basic purpose and filter options but lacks information on return format, pagination, or how parameters interact. Adequate but with gaps.

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 baseline is 3. The description lists some filters (property type, price, rooms, area, location) but does not add meaning beyond what the schema already provides for all 11 parameters. No additional semantic detail.

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 it searches real estate listings on willhaben.at, specifying apartment and house types for sale/rent, and lists filters. Differentiates from siblings like willhaben_search_cars and willhaben_search_jobs by focusing on real estate.

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 description implies usage for real estate queries but does not explicitly state when to use this tool versus alternatives like willhaben_search or willhaben_search_cars. No when-not or exclusion criteria provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aliildan/willhaben-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server