Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_property

Fetch a Rightmove property listing by ID to get price, address, bedrooms, EPC rating, agent reviews, and nearby schools.

Instructions

Get Rightmove property details. Returns one Rightmove listing by id: title, address, price and price_text, bedrooms, bathrooms, receptions, property type, status, description, features, floor plan, EPC rating, council tax band, tenure, agent reviews and nearby schools with Ofsted ratings. Removed or invalid ids return 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRightmove property ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the complete set of returned fields and the error behavior ('Removed or invalid ids return 404'). It does not mention auth needs or rate limits, but for a read-only lookup this is largely covered.

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 purpose, then the return-field list, then the error case. The long field enumeration is dense but earns its place since no output schema exists; nothing reads as filler.

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?

There is no output schema, so the description must describe return values itself, and it does so exhaustively (price, EPC, council tax, schools, etc.). Combined with the 404 note, an agent has enough to call it correctly, though it could say where the id originates.

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 100% with a single documented id parameter, so the schema does the heavy lifting and the baseline is 3. The description adds only the 404-on-invalid-id behavior, which gives some meaning to id validity but no format or sourcing detail.

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 states a specific verb ('Get') and resource ('Rightmove property details') and adds scope ('Returns one Rightmove listing by `id`'), which implicitly separates it from the search/autocomplete siblings. It does not name an alternative explicitly, so it stops short of full sibling differentiation.

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 only implied: the agent infers this is the fetch-by-known-id tool versus rightmove_search/rightmove_autocomplete. There is no explicit statement of when to use this over the sibling search tools or where the id should come from.

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

Deploy Server

Other Tools