Skip to main content
Glama

Search property listings

search_listings
Read-only

Live sale and rental listings from 24 property portals, every listing in one schema (price, currency, beds, baths, area, address, coordinates, photos, agent). Costs 1 credit per listing returned; a failed portal read costs nothing. Portal keys by country: AE: bayut (rent/sale), propertyfinder (sale/rent); CA: padmapper (rent); DE: immobilienscout24 (rent/sale), kleinanzeigen (rent/sale); ES: idealista (sale/rent), fotocasa (sale/rent); FR: leboncoin (sale/rent); GB: rightmove (sale/rent), zoopla (sale/rent); IE: daft (rent/sale); IT: idealista (sale/rent), immobiliare (sale/rent); NL: funda (sale/rent); PL: otodom (rent/sale); PT: idealista (sale/rent), imovirtual (sale/rent); SE: hemnet (sale); US: zillow (sale), realtor (sale/rent), zillow-rentals (rent), redfin (sale), redfin-rentals (rent), zumper (rent), padmapper (rent), apartments-com (rent), craigslist (rent/sale). Call list_sources first for the location format and the filters each portal takes. Returns at most 50 listings per call; when next_offset is in the answer, call again with it as offset for the next page (only the rows returned are charged). Pass a listing's url to get_listing for its full 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": {
      "source": "<source>",
      "location": "<location>"
    },
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRent or sale; default is the portal's first kind.
limitNoListings to return (1 credit each).
offsetNoListings to skip, for paging: use the `next_offset` of the previous answer. offset + limit may not pass 500.
sourceYesPortal key, e.g. 'zillow', 'rightmove', 'idealista'.
filtersNoOptional; only where the portal accepts them (see list_sources).
locationYesPlace as the portal expects it (see list_sources), e.g. 'Austin, TX', 'SW11', 'madrid', or a search link from the portal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "zillow",
      -  "realtor",
      -  "zillow-rentals",
      -  "redfin",
      -  "redfin-rentals",
      -  "zumper",
      -  "padmapper",
      -  "apartments-com",
      -  "craigslist",
      -  "rightmove",
      -  "zoopla",
      -  "idealista",
      -  "immobiliare",
      -  "immobilienscout24",
      -  "kleinanzeigen",
      -  "fotocasa",
      -  "funda",
      -  "daft",
      -  "otodom",
      -  "imovirtual",
      -  "hemnet",
      -  "bayut",
      -  "propertyfinder"
      -]New value: +[
      +  "zillow",
      +  "realtor",
      +  "zillow-rentals",
      +  "redfin",
      +  "redfin-rentals",
      +  "zumper",
      +  "padmapper",
      +  "apartments-com",
      +  "craigslist",
      +  "rightmove",
      +  "zoopla",
      +  "idealista",
      +  "immobiliare",
      +  "immobilienscout24",
      +  "kleinanzeigen",
      +  "fotocasa",
      +  "funda",
      +  "leboncoin",
      +  "daft",
      +  "otodom",
      +  "imovirtual",
      +  "hemnet",
      +  "bayut",
      +  "propertyfinder"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "zillow",
      -  "realtor",
      -  "zillow-rentals",
      -  "redfin",
      -  "redfin-rentals",
      -  "zumper",
      -  "padmapper",
      -  "apartments-com",
      -  "craigslist",
      -  "rightmove",
      -  "zoopla",
      -  "idealista",
      -  "immobiliare",
      -  "immobilienscout24",
      -  "kleinanzeigen",
      -  "fotocasa",
      -  "daft",
      -  "otodom",
      -  "imovirtual",
      -  "hemnet",
      -  "bayut",
      -  "propertyfinder"
      -]New value: +[
      +  "zillow",
      +  "realtor",
      +  "zillow-rentals",
      +  "redfin",
      +  "redfin-rentals",
      +  "zumper",
      +  "padmapper",
      +  "apartments-com",
      +  "craigslist",
      +  "rightmove",
      +  "zoopla",
      +  "idealista",
      +  "immobiliare",
      +  "immobilienscout24",
      +  "kleinanzeigen",
      +  "fotocasa",
      +  "funda",
      +  "daft",
      +  "otodom",
      +  "imovirtual",
      +  "hemnet",
      +  "bayut",
      +  "propertyfinder"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "zillow",
      -  "realtor",
      -  "zillow-rentals",
      -  "redfin",
      -  "redfin-rentals",
      -  "zumper",
      -  "padmapper",
      -  "apartments-com",
      -  "craigslist",
      -  "rightmove",
      -  "zoopla",
      -  "idealista",
      -  "immobilienscout24",
      -  "kleinanzeigen",
      -  "fotocasa",
      -  "daft",
      -  "otodom",
      -  "imovirtual",
      -  "hemnet",
      -  "bayut",
      -  "propertyfinder"
      -]New value: +[
      +  "zillow",
      +  "realtor",
      +  "zillow-rentals",
      +  "redfin",
      +  "redfin-rentals",
      +  "zumper",
      +  "padmapper",
      +  "apartments-com",
      +  "craigslist",
      +  "rightmove",
      +  "zoopla",
      +  "idealista",
      +  "immobiliare",
      +  "immobilienscout24",
      +  "kleinanzeigen",
      +  "fotocasa",
      +  "daft",
      +  "otodom",
      +  "imovirtual",
      +  "hemnet",
      +  "bayut",
      +  "propertyfinder"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Listings to skip, for paging: use the `next_offset` of the previous answer. offset + limit may not pass 500.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "zillow",
      -  "realtor",
      -  "zillow-rentals",
      -  "redfin",
      -  "redfin-rentals",
      -  "zumper",
      -  "padmapper",
      -  "apartments-com",
      -  "craigslist",
      -  "rightmove",
      -  "idealista",
      -  "immobilienscout24",
      -  "kleinanzeigen",
      -  "fotocasa",
      -  "daft",
      -  "otodom",
      -  "imovirtual",
      -  "hemnet",
      -  "bayut",
      -  "propertyfinder"
      -]New value: +[
      +  "zillow",
      +  "realtor",
      +  "zillow-rentals",
      +  "redfin",
      +  "redfin-rentals",
      +  "zumper",
      +  "padmapper",
      +  "apartments-com",
      +  "craigslist",
      +  "rightmove",
      +  "zoopla",
      +  "idealista",
      +  "immobilienscout24",
      +  "kleinanzeigen",
      +  "fotocasa",
      +  "daft",
      +  "otodom",
      +  "imovirtual",
      +  "hemnet",
      +  "bayut",
      +  "propertyfinder"
      +]
  5. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Goes well beyond the sparse readOnlyHint/openWorldHint annotations by disclosing cost mechanics (1 credit per listing returned, failed portal reads cost nothing, only returned rows charged) and a hard 50-per-call ceiling with a 500-row offset cap. However, it says nothing about latency, failure modes when a portal is blocked or a location string is misformatted, or how partial portal coverage surfaces in the response.

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

Conciseness3/5

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

Front-loaded well — purpose first, then cost, then routing. But the 24-portal country directory consumes roughly half the text and is largely redundant with list_sources, which the same description instructs the agent to call first; that block could be a single sentence pointing to list_sources output.

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?

With no output schema, the description still explains the return shape (per-listing fields, capped at 50 rows, `next_offset` for paging) and the follow-up path via get_listing. For a read-only, cross-portal search with 6 parameters, an agent has everything needed to call it correctly and handle pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by tying `offset` to the returned `next_offset` and deferring `location`/`filters` semantics to list_sources rather than guessing. The `type` default (portal's first kind) and the credit-per-row meaning of `limit` are also reinforced in prose, though the country/portal mapping is not stated as a rule linking `source` to `location`.

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?

Opens with a specific verb and resource plus differentiating scope: "Live sale and rental listings from 24 property portals, every listing in one schema (price, currency, beds, baths, area, address, coordinates, photos, agent)." It also distinguishes itself from both siblings by routing to list_sources (for formats/filters) and get_listing (for full records by url).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States an explicit prerequisite ordering ("Call list_sources first for the location format and the filters each portal takes") and gives a clear paging procedure ("when `next_offset` is in the answer, call again with it as `offset`"). It also names the country-to-portal keys needed to pick a `source`, and points to the alternative tool for a listing's full detail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.