Microburbs Australian Property Data

Listings · Listing photos

listings_images

Read-onlyIdempotent

The photos of one listing, as signed links you can download for 15 minutes.

What you get. Every photo we hold for the listing, main photo first, in the size you ask for, each as a link to the WebP file on our image store. The links need no key and expire at expires_at: download or cache the photos inside that window, and call again for fresh links. One call covers the whole gallery at a flat price per listing, priced separately from the listing data because photos are heavy.

Which photos. The same ones our listing page shows: the agency's own photography, never a listing portal's, and never logos, banners or office shots. A photo we have not copied to our store yet is left out (new listings' photos usually arrive within a day). A listing whose details we withhold — seen on only one major portal — has no photos here, and no listing_id elsewhere.

Get a listing_id from /v1/listings/search, the SA4 off-market bulk, or the suburb for-sale / for-rent endpoints.

Example: /v1/listings/cc74291e277ad596d6c41a6ce07077f1/images?size=large

Price: 5¢ 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": {
      "listing_id": "<listing_id>"
    },
    "name": "listings_images"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	small ≈ 640 px wide, medium ≈ 1200 px (default), large up to 2048 px.	medium
`listing_id`	Yes	The listing's `listing_id`, from any listings endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add the operationally important facts: the links are unauthenticated, they expire at `expires_at` after 15 minutes, results must be downloaded or cached within that window, and re-calling is the refresh path. It also discloses cost structure (5¢ per call, flat per listing, billed separately) and completeness caveats (not-yet-copied photos are omitted, new listings lag about a day).

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?

It is front-loaded with the key fact and organized under bold headers, which makes it skimmable rather than rambling. A few sentences are near-duplicative — the price is stated in the body and repeated as a closing line, and 'photos are heavy' is decorative. Still, the length is justified by the number of distinct facts conveyed.

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 must carry the return contract, and it does: signed WebP links, main photo first, ordered gallery, `expires_at`, and no-key access. What is missing is the response envelope itself — the JSON key names and whether results are an array or object — which an agent would need to parse reliably. For a two-parameter read tool that is a small gap.

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%, and the enum values for `size` are already documented with pixel widths in the schema, so the schema does the heavy lifting. The description adds only the request example with `?size=large` and the phrase 'in the size you ask for'. Baseline 3 is appropriate.

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 opening line names the exact resource (the photos of one listing) and the exact return form (signed links valid for 15 minutes). It also separates itself from sibling listing endpoints twice, by noting photos are 'priced separately from the listing data' and by listing which endpoints supply the required `listing_id`. An agent can pick this over `listings_search` or the suburb endpoints without opening any schema.

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 concrete entry conditions ('Get a `listing_id` from `/v1/listings/search`, the SA4 off-market bulk, or the suburb for-sale / for-rent endpoints') and a re-call rule ('call again for fresh links' once expired). It also documents when the tool is not useful: withheld listings seen on only one major portal have no photos here. It stops short of naming an alternate tool for those withheld cases, so it is a strong 4 rather than a 5.

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?