Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

redfin_search

Search Redfin property listings by location or region ID, with filters for price, beds, baths, status, and pagination to find homes for sale or sold.

Instructions

Search Redfin listings. Returns Redfin public listing search results. Pass region_id/region_type from autocomplete to skip location resolution.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page
statusNoListing status: for_sale or sold
locationNoDisplay location; resolved via autocomplete when region_id is omitted
min_bedsNoMinimum bedrooms filter
max_priceNoMaximum price filter
min_bathsNoMinimum bathrooms filter
min_priceNoMinimum price filter
region_idNoRedfin region id; skips location resolution when provided
region_typeNoRedfin region type, used with region_id (defaults to 6, city)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • changedInput schema / properties / region_id / description
      Previous value: -"Redfin region id from autocomplete"New value: +"Redfin region id; skips location resolution when provided"
    • changedInput schema / properties / region_type / description
      Previous value: -"Redfin region type from autocomplete (defaults to 6, city)"New value: +"Redfin region type, used with region_id (defaults to 6, city)"
    • addedInput schema / properties / region_type / enum
      Added value: +[
+  1,
+  2,
+  5,
+  6
+]
    • addedInput schema / properties / status / enum
      Added value: +[
+  "for_sale",
+  "sold"
+]
  2. Addedv1.1.0

TDQS

A3.5/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 behavioral burden. It does disclose the location-resolution fallback behavior (location resolved via autocomplete unless region_id is supplied), which is genuinely useful. However, it says nothing about pagination limits, result counts, ordering, or authentication, so coverage is only partial.

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?

Three tight sentences with no redundancy; the core purpose is front-loaded and the workflow hint follows. Every sentence earns its place.

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 nine-parameter search tool with no annotations and no output schema, the description is thin: it omits how results are paged, how many are returned, and what fields come back. The location-resolution hint is helpful but the definition is not complete enough to call the tool confidently without inspecting the schema.

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 all nine parameters are individually documented, so the baseline is 3. The description corroborates the region_id/region_type usage but adds no new filter semantics beyond what the schema already states.

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 Redfin listings') plus return scope ('public listing search results'), which is clear enough for an agent to know what it does. However, it does not differentiate itself from obvious siblings like redfin_property or redfin_similar, leaving the agent to infer that this is the broad search entry point.

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?

The tip to pass region_id/region_type from autocomplete to skip location resolution implies a two-step workflow, but there is no explicit when-to-use guidance or comparison to sibling tools (e.g., redfin_property for detail, redfin_region_trends for analytics). Usage context is only implied.

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