Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_search

Find UK properties for sale or rent on Rightmove by applying filters for location, price range, bedrooms, property type, and more to narrow results.

Instructions

Search Rightmove properties. Search for properties on Rightmove with filters for location, price, bedrooms, etc.

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

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates that the tool performs a search. It does not disclose the required location identifier format, default status/radius behavior, pagination, or what kind of result set the agent should expect.

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 and front-loaded, but the first and second sentences are largely redundant. The phrase 'etc.' is vague and the description misses the opportunity to add a compact, non-repetitive summary of key constraints like the location identifier requirement.

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

Completeness2/5

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

This is a high-complexity tool with 15 parameters, no annotations, and no output schema, yet the description is a bare two-sentence summary. It says nothing about how this search relates to rightmove_autocomplete, rightmove_property, or the more specific property-search siblings, leaving the agent under-equipped to select and invoke it correctly.

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 input schema already documents all 15 parameters thoroughly. The description's reference to 'location, price, bedrooms, etc.' adds no meaning beyond the schema, keeping this at the baseline score of 3.

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 names a specific verb and resource: 'Search Rightmove properties' and lists filter categories (location, price, bedrooms). It is clear at a basic level, but it does not explicitly distinguish this general search from sibling tools like rightmove_commercial_search, rightmove_new_homes_search, or rightmove_student_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus alternatives. The description provides no exclusions, prerequisites, or mention of the many rightmove_* siblings, so an agent cannot determine whether this is the right general search or whether a more specific search tool should be used.

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