Microburbs Australian Property Data

Suburb · Current rental listings

suburbs_listings_for_rent

Read-onlyIdempotent

Rental listings live right now in the suburb, with address, weekly rent and the advertised rent line, beds/baths/cars, coordinates, an off_market flag and the leasing agency. Same paging, filters and withholding rule as for-sale.

Price: 20¢ 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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_listings_for_rent"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max listings to return (default 30, max 200). `total` always reports the full match count.
`offset`	No	Listing offset — page with `limit`. `next_offset` in the response is the value for the next page (null on the last).
`verbose`	No	Include the agent's full ad-copy in `attributes.description`. Off by default.
`off_market`	No	Only return OFF-MARKET listings: not on the major listing portals, sourced from the agency's own site, and still believed live — our Property Finder's 'Off market only' rule. Default false returns every listing, each carrying its own `off_market` flag. `total` counts the filtered set.
`suburb_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / off_market / description

Previous value: -"Only return OFF-MARKET listings: not on realestate.com.au or Domain, sourced from the agency's own site, and still believed live — the Microburbs property finder's 'Off market only' rule. Default false returns every listing, each carrying its own `off_market` flag. `total` counts the filtered set."New value: +"Only return OFF-MARKET listings: not on the major listing portals, sourced from the agency's own site, and still believed live — our Property Finder's 'Off market only' rule. Default false returns every listing, each carrying its own `off_market` flag. `total` counts the filtered set."

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Listing offset — page with `limit`. `next_offset` in the response is the value for the next page (null on the last).",
+  "minimum": 0,
+  "type": "integer"
+}

AddedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the exact payload contents (including the per-listing off_market flag), an implied withholding rule, and an explicit cost of 20¢ per call, which matters for an agent budgeting calls. It stops short of explaining what the withholding rule actually removes.

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?

Roughly two sentences plus a price line, front-loaded with what the tool returns before the convention transfer and the cost. Every clause carries information; nothing is padding.

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 usefully enumerates the returned fields, which is the main completeness burden here, and the billing line covers cost expectations. The remaining gap is the undefined 'withholding rule' and no guidance on suburb_name matching, which for a single-required-parameter lookup tool is a modest omission.

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 80%, so limit, offset, verbose and off_market already carry detailed descriptions and the baseline of 3 applies. The description's reference to 'paging, filters and withholding rule' echoes the schema rather than adding new meaning, and suburb_name remains undocumented in both places (no matching/format rules).

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 and resource ('Rental listings live right now in the suburb') and enumerates the returned fields (address, weekly rent, rent line, beds/baths/cars, coordinates, off_market flag, agency). It also explicitly contrasts with the for-sale counterpart ('Same paging, filters and withholding rule as for-sale'), so an agent can separate it from suburbs_listings_for_sale without opening either schema.

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?

Usage is implied rather than stated: an agent infers this is the tool for live rental stock in a named suburb, and 'Same paging, filters and withholding rule as for-sale' transfers conventions from a sibling. There is no explicit when-not guidance and no mention of how it relates to listings_search or suburbs_market_median_rent for related questions.

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?