SiteCheck Jobs & Property

Zoopla homes for sale or to rent in an area: headline

realestate_zoopla

Read-only

Zoopla (UK) homes for sale or to rent in an area: headline (e.g. '3 bed end terrace house for sale'), price (GBP; monthly rent for lettings), address, coordinates, bedrooms, bathrooms, floor size (sq ft), property type, short description, image and link, about 25 per page (page 1 to 20). From zoopla.co.uk's public search pages via a premium residential proxy. Related tools on this server, for a different need: realestate_hemnet when you need Hemnet homes for sale in an area: address, housing form; realestate_seloger when you need SeLoger homes for sale or rent in a town: listing id. Price: $0.005 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "area": "<area>"
    },
    "name": "realestate_zoopla"
  }
}

Input Schema

Name	Required	Description
`area`	Yes	Area slug as in zoopla.co.uk/for-sale/property/<area>/, e.g. london, manchester, bristol, sw11
`page`	No	Results page 1 to 20 (default 1)
`type`	No	for-sale or to-rent (default for-sale)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the data source (zoopla.co.uk public search pages via a premium residential proxy), the pagination ceiling (~25 per page, page 1–20), and the billing model ($0.005 USDC per successful call via x402 on Base, Solana or Arc; failures not charged). Those are real operational constraints an agent needs before calling.

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?

Front-loaded with the resource and returned fields, then source, then alternatives, then pricing — a sensible information hierarchy in one tight paragraph. The long field enumeration and proxy/payment details are dense but each earns its place for a paid scraping tool.

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 an output schema covering return values, full schema descriptions, and readOnly/openWorld annotations, the description supplies everything else an agent needs: geography, currency/rent semantics, pagination limits, data provenance, cost model, and sibling routing.

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 baseline is 3, but the description adds meaning the schema does not: price is in GBP and represents monthly rent for lettings, and results are about 25 per page, which quantifies the effect of the page parameter. It doesn't clarify page/type interactions (e.g. page applicability to rentals), so it stops short of 5.

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 names a specific verb+resource ('Zoopla (UK) homes for sale or to rent in an area') and enumerates the returned fields (headline, price, address, coordinates, bedrooms, bathrooms, floor size, type, description, image, link). It also names its international siblings (realestate_hemnet, realestate_seloger) so the agent can tell the UK Zoopla tool apart from other property sources.

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

Usage Guidelines4/5

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

It explicitly routes the agent to alternatives 'for a different need' — Hemnet for Swedish listings and SeLoger for French towns — giving clear geographic selection criteria. It does not mention other UK-relevant siblings such as realestate_rightmove_property or realestate_openrent_uk_listings, so coverage is good but not exhaustive.

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

All SiteCheck Jobs & Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?