Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_search

Search Rightmove listings by location and filter by sale or rental status, price, bedrooms, bathrooms, property type, radius, and must-have features. Returns total and key property details.

Instructions

Search Rightmove properties. Searches Rightmove listings for a required location id, for sale (default) or to_let, 1-indexed by page. Filter by price, bedrooms, bathrooms, property_type, radius, must_have, dont_show and tenure_types; sort defaults to newest_listed. Returns total and results with price, address, beds, baths, size and tenure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page (default 1)
sortNoResult sort order, default newest_listed
radiusNoSearch radius in miles around location, default 0 (this area only)
statusNoListing status (default for_sale)
locationYesRightmove location identifier from autocomplete
dont_showNoExclude listings with these attributes. Accepts one or more comma-separated values.
max_priceNoMaximum price in whole GBP units, not pence
min_priceNoMinimum price in whole GBP units, not pence
must_haveNoRequire listings to have these attributes. Accepts one or more comma-separated values.
max_bedroomsNoMaximum bedrooms
min_bedroomsNoMinimum bedrooms
tenure_typesNoTenure filter. Accepts one or more comma-separated values.
max_bathroomsNoMaximum bathrooms
min_bathroomsNoMinimum bathrooms
property_typeNoProperty type filter. Accepts one or more comma-separated values. private-halls (Student Halls) mainly returns results for status=to_let.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.17.5
    • addedInput schema / properties / dont_show
      Added value: +{
+  "description": "Exclude listings with these attributes. Accepts one or more comma-separated values.",
+  "enum": [
+    "newHome",
+    "retirement",
+    "sharedOwnership",
+    "auction"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / must_have
      Added value: +{
+  "description": "Require listings to have these attributes. Accepts one or more comma-separated values.",
+  "enum": [
+    "garden",
+    "parking",
+    "retirement",
+    "newHome",
+    "sharedOwnership",
+    "auction"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / property_type / description
      Previous value: -"Property type filter"New value: +"Property type filter. Accepts one or more comma-separated values. private-halls (Student Halls) mainly returns results for status=to_let."
    • addedInput schema / properties / property_type / enum
      Added value: +[
+  "detached",
+  "semi-detached",
+  "terraced",
+  "flat",
+  "bungalow",
+  "land",
+  "park-home",
+  "private-halls"
+]
    • addedInput schema / properties / radius
      Added value: +{
+  "description": "Search radius in miles around location, default 0 (this area only)",
+  "enum": [
+    0,
+    0.25,
+    0.5,
+    1,
+    3,
+    5,
+    10,
+    15,
+    20,
+    30,
+    40
+  ],
+  "type": "number"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Result sort order, default newest_listed",
+  "enum": [
+    "lowest_price",
+    "highest_price",
+    "newest_listed",
+    "oldest_listed"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / status / enum
      Added value: +[
+  "for_sale",
+  "to_let"
+]
    • addedInput schema / properties / tenure_types
      Added value: +{
+  "description": "Tenure filter. Accepts one or more comma-separated values.",
+  "enum": [
+    "FREEHOLD",
+    "LEASEHOLD",
+    "SHARE_OF_FREEHOLD"
+  ],
+  "type": "string"
+}
  2. 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 well: it discloses default values (for_sale, radius 0, sort newest_listed), that paging is 1-indexed, and what the response contains (`total` plus price, address, beds, baths, size, tenure). It omits any auth or rate-limit context, which is a minor gap for a scraper-backed search.

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?

Two dense sentences, front-loaded with the core action and required input, then filters and return shape. Efficient with little waste, though the parameter enumeration is a long run-on list.

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?

For a 15-parameter search with no output schema, the description supplies defaults, pagination semantics, and a return-field summary, which is enough to call it correctly. It stops short of explaining the residential/commercial/student/new-homes split that the sibling set implies.

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%, so the schema already documents all 15 parameters, making 3 the baseline. The description adds only marginal value, mainly the 1-indexed page convention and a rolled-up list of which filters exist.

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?

States a specific verb and resource ('Search Rightmove properties'), and pins down scope by noting the required `location` id and sale/to_let modes. It does not, however, distinguish itself from close siblings such as rightmove_commercial_search, rightmove_new_homes_search, or rightmove_student_search, so an agent must infer which search applies.

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?

Signals when the tool applies implicitly via 'required location id', the default `for_sale`, and the `to_let` alternative, but gives no explicit when-to-use rules or pointers to the specialized sibling searches. Usage is implied rather than stated.

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