Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rightmove_commercial_search

Find commercial properties for sale or let on Rightmove using filters for location, price, size, and property type.

Instructions

Search Rightmove commercial property. Search Rightmove's commercial property listings for sale or to let, with price, floor-area (sq ft), and commercial-property-type filters. For to-let listings the price amount follows the listing's own frequency (monthly or yearly).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page (default 1)
statusNoListing status (default buy)
locationYesRightmove location identifier from autocomplete
max_sizeNoMaximum floor area in square feet
min_sizeNoMinimum floor area in square feet
max_priceNoMaximum price in whole GBP units, not pence
min_priceNoMinimum price in whole GBP units, not pence
property_typeNoCommercial property type filter. Accepts one or more comma-separated values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • changedInput schema / properties / property_type / description
      Previous value: -"Commercial property type filter (e.g. office, retail, industrial, warehouse, land, hotel, leisure)"New value: +"Commercial property type filter. Accepts one or more comma-separated values."
    • addedInput schema / properties / property_type / enum
      Added value: +[
+  "business-park",
+  "office",
+  "serviced-office",
+  "convenience-store",
+  "hairdresser-barber-shop",
+  "post-office",
+  "retail_property_high_street_",
+  "retail_property_out_of_town_",
+  "retail_property_pop_up_",
+  "retail_property_retail_park_",
+  "retail_property_shopping_centre_",
+  "shop",
+  "showroom",
+  "trade-counter",
+  "bar-nightclub",
+  "cafe",
+  "leisure-facility",
+  "guest-house",
+  "hotel",
+  "hospitality",
+  "pub",
+  "restaurant",
+  "takeaway",
+  "other",
+  "distribution-warehouse",
+  "factory",
+  "heavy-industrial",
+  "industrial-park",
+  "light-industrial",
+  "storage",
+  "warehouse",
+  "workshop",
+  "industrial-development",
+  "land",
+  "farm",
+  "residential-development",
+  "healthcare-facility",
+  "childcare-facility",
+  "commercial-property",
+  "garage",
+  "mixed-use",
+  "commercial-development",
+  "petrol_station",
+  "place_of_worship"
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "buy",
+  "let"
+]
  2. Addedv1.16.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses one important behavioral nuance: for to-let listings, the price amount follows the listing's own frequency (monthly or yearly). It does not mention default values (like status defaulting to 'buy'), pagination, or read-only nature, though the search intent is implicit. The pricing clarification is valuable but limited.

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?

Two sentences with no redundancy. The first sentence establishes the purpose and filters, the second adds a precise pricing nuance. Information is front-loaded and every word earns its place.

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 search tool with 8 parameters and no output schema, the description covers the essential purpose, filter types, and a key pricing behavior. It does not explain response format, pagination, or default status, but these are not critical for invoking the tool correctly. The description is adequate for an agent to decide to call it.

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?

The schema provides 100% description coverage for all 8 parameters, so the baseline is 3. The description adds a specific clarification about the price parameter for to-let listings (frequency follows listing), which is useful beyond the schema, but it does not add meaning to other parameters. The addition is minor, so it stays at baseline.

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 ('Search'), a specific resource ('Rightmove's commercial property listings'), and clearly defines the scope with filters for sale/to-let, price, floor-area, and property type. The commercial focus distinguishes it from sibling tools like rightmove_search, rightmove_new_homes_search, and 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 Guidelines4/5

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

The description clearly implies its use case for commercial property searches, differentiating it from residential or other Rightmove searches. However, it does not explicitly name alternatives or state when not to use this tool, relying on the name and content for context.

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