Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

redfin_search

Search Redfin listings using a location or region ID; filter by status, price, beds, and baths to receive normalized JSON results for for-sale and sold properties.

Instructions

Search Redfin listings. Returns normalized Redfin public listing search results from Redfin's credential-free region CSV endpoint. Pass region_id/region_type from autocomplete to skip location resolution.

Input Schema

TableJSON 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.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the data source (Redfin credential-free region CSV endpoint), that results are normalized and public, and that location resolution can be skipped with region_id/region_type. It doesn't cover pagination or defaults, but it provides meaningful behavioral context beyond the schema.

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?

Three short sentences, purpose first, with the endpoint and a usage tip following. Slight redundancy between 'Search Redfin listings' and 'Returns ... search results' but no wasted words overall.

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 9-parameter search tool with no annotations and no output schema, the description covers source, auth, and location resolution but leaves out response shape, pagination behavior, and default status. The schema covers parameter meanings, so this is adequate but not complete.

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 baseline is 3. The description reinforces region_id/region_type behavior ('skip location resolution') but adds no information beyond the schema's own descriptions for those parameters. No other parameters are discussed.

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.' The second sentence clarifies it returns normalized public listing search results from a specific endpoint. It doesn't explicitly contrast with sibling tools like redfin_property or redfin_similar, but the resource and scope are clear.

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?

Gives actionable context for using region_id/region_type from autocomplete to skip location resolution. It does not name alternatives or state when to prefer this over redfin_property, redfin_similar, redfin_estimate, or redfin_region_trends, so usage guidance is implied rather than explicit.

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