MarketCode

Photographs, floorplans and brochures

property_media

Read-onlyIdempotent

Photographs, floorplans, EPC graphs and brochures for a property, from the
listings we have crawled. Narrow with `types` — a comma-separated list of
`image`, `floorplan`, `epc`, `brochure`, `virtual_tour`.

EVERY LINK IS OURS AND EVERY LINK EXPIRES. Do not store them; call this
again when you need fresh ones, and set `ttl_seconds` to match how long the
surface you are building keeps them on screen. The portal's own URL is
never returned, so a saved response cannot turn into a hotlink later.

COVERAGE IS UNEVEN AND THE COUNTS TELL YOU. We hold the actual files for
floorplans and brochures only, and for a minority of those; everything else
— including all photographs — is a link that redirects to the source.
`n_held_by_us` against `n_redirected` says which is which for this property,
and `delivery` says it per item. Do not describe a property as having no
photographs when the answer is `no_media`: about a third of listings never
resolve to a UPRN, so that is as often a matching gap as an absence.

Each item carries the portal and host it came from — useful when a user
asks where a picture is from, and when one source turns out to be bad.
UK only. Free. Keyed on a UPRN, not an address: call `address_autocomplete` (free) to narrow, then `address_resolve` to get one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uprn`	Yes
`types`	No
`ttl_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.9/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), but the description adds substantial unstated behavior: every link expires and the portal URL is never returned (anti-hotlinking), coverage is uneven with held vs redirected files, and no_media is often a UPRN-matching gap rather than true absence. ttl_seconds is framed as a caller-controlled freshness policy.

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 resource and the `types` filter, then the expiry warning, coverage caveat, and routing. Every sentence is relevant, but the caps-lock emphasis and dense coverage paragraph make it longer than strictly necessary for an agent to act on.

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?

An output schema exists so return values needn't be fully re-explained, yet the description still names the discriminating fields (n_held_by_us, n_redirected, delivery, no_media) so an agent can interpret coverage. Combined with routing instructions and the freshness model, nothing needed to invoke it correctly is missing.

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?

With 0% schema description coverage, the description carries the load: it enumerates the valid `types` values (image, floorplan, epc, brochure, virtual_tour) as a comma-separated list and explains `ttl_seconds` as matching how long the consuming surface keeps links on screen. It also clarifies `uprn` semantics as a keyed identifier rather than an address.

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 resource (photographs, floorplans, EPC graphs, brochures) tied to a crawled-listing scope, with the verb of retrieval implied clearly. It distinguishes itself from siblings by noting it is keyed on a UPRN rather than an address, unlike address_* tools.

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?

Gives explicit workflow guidance: use address_autocomplete to narrow then address_resolve to obtain the UPRN, and call this tool fresh each time links are needed rather than storing them. It also states the UK-only and free constraints, so an agent knows the operating envelope.

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

All MarketCode 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?