UK Property Data

rightmove_listing

Read-only

Full detail for a single Rightmove listing.

property_id is the numeric Rightmove property ID (the digits at the end of a rightmove.co.uk/properties/... URL), max 12 digits. Full URLs are not accepted. include_images fetches and embeds photos and floorplans as MCP image content. max_images caps the number of property photos (default 3); floorplans always included.

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": {
      "property_id": "<property_id>"
    },
    "name": "rightmove_listing"
  }
}

Input Schema

Name	Required	Description	Default
`max_images`	No
`property_id`	Yes
`include_images`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 24, 2026

addedInput schema / properties / property_id
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / property_url_or_id
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / required

Previous value: -[
-  "property_url_or_id"
-]New value: +[
+  "property_id"
+]

Changed2 schema fields changedMay 9, 2026

addedInput schema / properties / max_images

Added value: +{
+  "default": 3,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 9, 2026
- addedInput schema / properties / include_images
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

Changed5 schema fields changedMay 9, 2026

removedInput schema / properties / include_images

Removed value: -{
-  "default": false,
-  "description": "Include image URLs in the response (default False)",
-  "type": "boolean"
-}

removedInput schema / properties / max_images

Removed value: -{
-  "default": 8,
-  "description": "Max image URLs to include when include_images=True (default 8)",
-  "type": "integer"
-}

removedInput schema / properties / property_id

Removed value: -{
-  "description": "Rightmove property URL (e.g. \"https://www.rightmove.co.uk/properties/12345678\") or numeric ID (e.g. \"12345678\")",
-  "type": "string"
-}

addedInput schema / properties / property_url_or_id
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

Previous value: -[
-  "property_id"
-]New value: +[
+  "property_url_or_id"
+]

AddedMay 8, 2026
RemovedMay 3, 2026

Changed1 schema field changedApr 20, 2026

addedInput schema / properties / property_id / description

Added value: +"Rightmove property URL (e.g. \"https://www.rightmove.co.uk/properties/12345678\") or numeric ID (e.g. \"12345678\")"

First observedApr 20, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds meaningful behavior context: include_images fetches and embeds photos/floorplans, and max_images limits photos but not floorplans. However, it does not disclose potential response size, fetching cost, rate limits, or what 'full detail' contains beyond images.

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?

The description is compact and every sentence earns its place. The primary purpose is front-loaded, and parameter details are separated cleanly into bullet-style lines. There is no unproductive fluff or repeated schema information.

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?

Given there is no output schema, the description covers what an agent needs to invoke the tool correctly: the input format, constraints, and optional behavior around images. It remains slightly vague about the exact return payload beyond calling it 'Full detail,' but as a single-listing fetch tool with read-only annotations, there is no critical missing selection or invocation context.

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?

Schema description coverage is 0%, so the description bears full responsibility for explaining parameters. It does this well: property_id is defined as a numeric Rightmove ID with URL examples, a 12-digit maximum, and rejection of full URLs; include_images is tied to MCP image content; max_images nuances are clear (photos only, default 3, floorplans always included). This is excellent compensation for a bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns 'Full detail for a single Rightmove listing,' which is a specific resource and scope. It is not a formal verb phrase, but the intent is unambiguous. It differentiates itself from a list/search tool by emphasizing a single listing, though it does not name sibling tools.

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?

The description implies usage: to get full detail for one specific Rightmove listing using a numeric property ID. However, it does not explicitly say when to use this tool over rightmove_search or other siblings, nor does it mention that property_id would typically come from a search result. Usage context is present but mostly implicit.

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

All UK 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.