Skip to main content
Glama

Microburbs Australian Property Data

Search listings in a region

listings_search
Read-onlyIdempotent

Search the listings live right now across a region, with the filters of our Property Finder, and get back the same rows as the suburb listings endpoints.

What it is. Our Property Finder as one API call: every property for sale (or for rent) in the area you name, one row per property, filtered and sorted the way the finder does it, with each listing's address, price line, beds, baths and car spaces, land and floor area, coordinates, an off_market flag, the agency's own listing page and the named agents.

Where to search — give exactly one:

  • suburbs — up to 20 suburb names, comma-separated;

  • sa3, sa4 or lga — a whole statistical area or council;

  • lat + lon + radius_m — a circle of up to 10 km.

Filters (all optional, combine freely): min_/max_ bedrooms, bathrooms, car_spaces, price and land_size; property_type (house / unit); off_market; and listed_after / listed_before on the date the listing was first advertised. A listing that does not state a value never matches a filter on it. A listing seen on only one major portal, with no agency page of its own, keeps its address, type and agency name but not its advertised facts — and so never matches a filter on those facts and sorts last on them.

Sort and page. sort = newest (default), price, bedrooms or land_size, with order asc / desc. Pages of up to 25 rows: total is the full match count and next_offset the next page's offset. Each page is one call at a flat price.

Examples

  • Three-bedroom houses under $900,000 in two suburbs: /v1/listings/search?suburbs=Belmont North,Belmont (NSW)&property_type=house&min_bedrooms=3&max_price=900000

  • Off-market listings in a council area, newest first: /v1/listings/search?lga=Lake Macquarie&off_market=true

  • Rentals within 2 km of a point, cheapest first: /v1/listings/search?status=rent&lat=-32.97&lon=151.67&radius_m=2000&sort=price&order=asc

Price: 30¢ per call.

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": "listings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoCentre latitude for a radius search (WGS84).
lgaNoA council (LGA) name, as `/v1/lga/list` returns it (e.g. `Lake Macquarie`): searches the suburbs whose main council it is.
lonNoCentre longitude for a radius search (WGS84).
sa3NoAn SA3 name: searches the suburbs whose main SA3 it is (e.g. `Lake Macquarie - East`).
sa4NoAn SA4 name, as `/v1/sa4/list` returns it (e.g. `Newcastle and Lake Macquarie`).
sortNoSort key. Listings without the value sort last either way.newest
limitNoRows per page, at most 25. `total` always reports the full match count.
orderNoSort direction.desc
offsetNoRow 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.
statusNo`sale` for listings on the market now (default), `rent` for rentals live now.sale
suburbsNoComma-separated suburb names, up to 20 — spelt as the suburb endpoints take them (`Belmont North`, `St Kilda (Vic.)`).
verboseNoInclude the agent's full ad copy in `attributes.description`. Off by default — it averages ~1.5 KB per listing.
radius_mNoRadius in metres around `lat`/`lon`, 100–10000.
max_priceNoAUD. Weekly rent when `status=rent`.
min_priceNoAUD. Weekly rent when `status=rent`. Listings with no stated price never match a price filter.
off_marketNoOnly OFF-MARKET listings: on none of the major listing portals, sourced from the agency's own site, and still believed live — our Property Finder's 'Off market only' rule.
listed_afterNoOnly listings first advertised on or after this date (YYYY-MM-DD).
max_bedroomsNo
min_bedroomsNo
listed_beforeNoOnly listings first advertised on or before this date.
max_bathroomsNo
max_land_sizeNoAdvertised land size, m².
min_bathroomsNo
min_land_sizeNoAdvertised land size, m². Listings that do not state one never match.
property_typeNo`house` (houses, cottages, acreage) or `unit` (apartments, units, townhouses, villas, terraces, duplexes, studios). Omit for both.
max_car_spacesNo
min_car_spacesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive search. The description adds substantial behavioral context beyond annotations: listings missing advertised facts never match filters and sort last, pagination uses total and next_offset, each page is a separate call, and each call costs 30 cents. It also discloses the cost of verbose mode at roughly 1.5 KB per listing.

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?

The description is long but well-structured with headings, bold labels, bullet points, and concrete examples. Most sentences earn their place given the 27-parameter surface area, though it could be trimmed slightly without losing essential meaning.

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?

For a 27-parameter search tool with no output schema, the definition is remarkably complete. It covers location modes, filters, sort and paging behavior, response contents, data-quality caveats, pricing, and examples, leaving little ambiguity about how to call it correctly.

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

Parameters5/5

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

The description adds important cross-parameter semantics not captured fully by the 78% schema coverage: exactly one location selector must be supplied, filters combine freely, missing values never match filters, price means weekly rent when status=rent, and sort orders place missing values last. It also explains pagination limits and the meaning of off_market in practical terms.

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 states a specific verb, resource, and scope: 'Search the listings live right now across a region.' It further distinguishes the tool by describing it as 'our Property Finder as one API call' and noting it returns 'the same rows as the suburb listings endpoints,' which helps separate it from sibling suburb-specific tools.

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 gives clear usage conditions, especially that exactly one location selector must be used among suburbs, sa3, sa4, lga, or lat/lon/radius. It also explains optional filters and supplies three concrete examples. However, it does not explicitly say when to choose this tool over sibling tools such as suburbs_finder_search or suburbs_listings_for_sale.

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.

Resources