Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_new_homes_search

Search Rightmove new-build homes for sale by location and filters like price, bedrooms, bathrooms, and property type. Returns individual plots and homes with development flags.

Instructions

Search Rightmove new homes for sale. Search Rightmove's new-homes-for-sale listings for a location, with price, bedroom, bathroom, and property-type filters. Results are individual new-build homes and plots (with development flags), not development-level cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page (default 1)
locationYesRightmove location identifier from autocomplete
max_priceNoMaximum price in whole GBP units, not pence
min_priceNoMinimum price in whole GBP units, not pence
max_bedroomsNoMaximum bedrooms
min_bedroomsNoMinimum bedrooms
max_bathroomsNoMaximum bathrooms
min_bathroomsNoMinimum bathrooms
property_typeNoProperty type filter. Accepts one or more comma-separated values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • changedInput schema / properties / property_type / description
      Previous value: -"Property type filter (e.g. detached, flat, apartment, semi-detached, terrace, bungalow)"New value: +"Property type filter. Accepts one or more comma-separated values."
    • addedInput schema / properties / property_type / enum
      Added value: +[
+  "detached",
+  "semi-detached",
+  "terraced",
+  "flat",
+  "bungalow",
+  "land",
+  "park-home"
+]
  2. Addedv1.16.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It communicates that this is a read-only search and reveals result granularity (individual homes/plots with development flags). However, it doesn't discuss pagination behavior, response format, required location provenance, or any rate-limiting/auth concerns. For a search operation this is adequate but not a strong disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the first sentence ('Search Rightmove new homes for sale.') is largely redundant with the second sentence and the tool name. The third sentence adds valuable granularity information. Every sentence should earn its place; the opening does not, so it can't be rated higher.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 9 parameters, no output schema, and no annotations, the description covers the purpose and result granularity, but does not describe return fields, pagination behavior, or how 'location' should be obtained (though the schema mentions autocomplete). It is sufficient for basic invocation but leaves gaps for an agent trying to interpret results.

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 each parameter already has a clear description. The tool description lists filter categories (price, bedroom, bathroom, property-type) that map onto the schema but adds no constraints, default behavior, or syntax details beyond what the schema provides. Baseline 3 applies.

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 and resource: 'Search Rightmove's new-homes-for-sale listings'. It also specifies the available filter dimensions (price, bedrooms, bathrooms, property type) and the result granularity ('individual new-build homes and plots... not development-level cards'), which clearly distinguishes it from broader siblings like rightmove_search and rightmove_commercial_search.

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?

The description gives clear context for when to use this tool: whenever new-homes-for-sale listings are needed. It also draws an exclusion boundary by stating the results are not development-level cards, implying the user should not expect development-level aggregation. It doesn't explicitly name sibling alternatives (e.g., rightmove_search for resale), so it stops short of a 5.

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