Microburbs Australian Property Data

Off-market listings in an SA4 (bulk)

listings_off_market

Read-onlyIdempotent

Every off-market listing in an SA4, in pages of up to 250 — the bulk way to take a whole region's off-market stock.

Off market means our Property Finder's rule: the listing is on none of the major listing portals, the agency's own site is a source (an aggregator republishing someone else's listing does not count), and our evidence that it is still live is current. These are listings a portal search will not show you.

Same rows as the suburb listings endpoints and /v1/listings/search, newest first, with total, next_offset and the same withholding rule. sa4 is spelt as /v1/sa4/list returns it, e.g. Newcastle and Lake Macquarie. status=rent for off-market rentals. For off-market listings in a smaller area, or with filters, use /v1/listings/search?off_market=true.

Example: /v1/listings/off-market?sa4=Newcastle and Lake Macquarie

Price: 300¢ per call.

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": {
      "sa4": "<sa4>"
    },
    "name": "listings_off_market"
  }
}

Input Schema

Name	Required	Description	Default
`sa4`	Yes	The SA4, spelt as `/v1/sa4/list` returns it.
`limit`	No	Rows per page, at most 250. `total` always reports the full match count.
`offset`	No	Row offset for paging. `next_offset` in the response is the value for the next page (null on the last). Each page is a separate call.
`status`	No	`sale` for listings on the market now (default), `rent` for rentals live now.	sale
`verbose`	No	Include the agent's full ad copy in `attributes.description`. Off by default — it averages ~1.5 KB per listing.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds genuinely new behavior: the per-call price (300¢), the fact that each page is a separately billed call, that results come newest-first with the same withholding rule as other listing endpoints, and that portal searches will not surface these rows.

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 payload and a scannable definition block, then routing, then a concrete example, then price. Slightly more prose than strictly needed (the parenthetical about aggregators), but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the return-shape burden and does so reasonably: it names 'total', 'next_offset', the shared withholding rule and what 'verbose' adds. It does not show a sample row or field list, which would have closed the remaining gap for an agent assembling a response.

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 coverage is 100%, so every parameter is already documented, including the sa4 spelling, limit cap, offset/next_offset paging and the ~1.5 KB cost of 'verbose'. The description restates the sa4 format and status=rent but adds no syntax or interpretation beyond the schema, so the baseline of 3 applies.

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 a specific verb+resource+scope: 'Every off-market listing in an SA4, in pages of up to 250'. It also defines the distinguishing concept of 'off market' (not on major portals, agency site as source, live evidence current), which an agent cannot infer from the name, and names the sibling route for the narrower case.

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?

Explicit routing: use this for whole-region bulk off-market pulls, but use '/v1/listings/search?off_market=true' for a smaller area or when filters are needed. It also tells the agent 'status=rent for off-market rentals', so the sale/rent decision is pre-answered rather than inferred from the enum default.

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

All Microburbs Australian Property Data 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?