highbrow_fame data APIs (pay per call)

Property listings on one portal

properties_search

Read-only

Property listings from one portal per call: Redfin and Realtor.com (United States), Property Finder (UAE), Magicbricks and NoBroker (India), Property24 (South Africa) or Emlakjet (Turkey). Returns price, address, beds, baths, area, property type, listing status and link. Suited to home search and housing-market questions. $0.02 per call, up to 25 listings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "properties_search"
  }
}

Input Schema

Name	Required	Description
`site`	No	Portal key from /properties/sites, e.g. redfin, realtor, propertyfinder, property24.
`input`	No	Advanced: a JSON object with the site's own filters; GET /sites lists them per site.
`limit`	No	Maximum results (default 20).
`query`	No	Keywords, e.g. "garden".
`minArea`	No	Minimum area (m² or ft² as the portal uses).
`location`	No	City, region or postcode as the site understands it, e.g. "Berlin".
`maxPrice`	No	Maximum price in the portal currency.
`minPrice`	No	Minimum price in the portal currency.
`minRooms`	No	Minimum rooms or bedrooms.
`searchUrl`	No	Instead of query/location: a full search-results link from the site, with its filters.
`transaction`	No	sale or rent (where the portal has both).
`propertyType`	No	A property type the portal accepts (see /properties/sites).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds genuinely new behavior: $0.02 per call and a 25-listing ceiling. Cost per invocation is the kind of detail annotations cannot convey and that directly affects agent strategy. It omits any note on rate limits, portal-side failures, or what happens when a site key is invalid.

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?

Three sentences, front-loaded with the core purpose and coverage, followed by returns and pricing. The site-to-country enumeration is dense but load-bearing for portal selection. No filler sentences.

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 12-parameter, zero-required tool this is decent but not complete: the description never addresses the real risk that an agent calls it with no location/query/searchUrl and gets an unfiltered result. It also defers site-key discovery to the schema's reference to /properties/sites without flagging that a valid key is mandatory in practice.

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 baseline is 3. The description reinforces the single-portal constraint and the currency semantics of price filters, but adds no syntax or format detail beyond what the schema fields already state. The listed output fields inform expectations rather than parameter meaning.

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?

Opens with a precise verb+resource+scope: 'Property listings from one portal per call,' then enumerates which portals map to which countries. It also states the returned fields (price, address, beds, baths, area, type, status, link), so an agent knows exactly what it gets. It stops short of naming a sibling it displaces, so 4 rather than 5.

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?

'Suited to home search and housing-market questions' gives a use context, and 'one portal per call' implies you call repeatedly for multi-country coverage. But there is no when-not guidance, no explanation of how to obtain valid site keys, and no statement about which parameters constitute a workable minimal call given that none are required.

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

All highbrow_fame data APIs (pay per call) 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?