Skip to main content
Glama
chrischall

redfin-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search Redfin listings

redfin_search_properties
Read-onlyIdempotent

Search Redfin for-sale listings by city, ZIP, neighborhood, or address with price, bed, and bath filters. Returns matching homes with details and Redfin URLs.

Instructions

Search Redfin listings by location (city, ZIP, neighborhood, or full street address) and optional filters. Resolves the location via Redfin's autocomplete then queries the gis API; full street addresses short-circuit to the single matched home (no gis call). Returns matching properties with price, beds/baths, sqft, year built, address, and the Redfin home URL. resolved_as is 'region' / 'address'. coverage is 'full' (gis indexed this region), 'profile_only' (Redfin has profiles for individual addresses here but search isn't indexed — use redfin_get_by_address per property), or 'none'. result_cap_hit: true signals the result page is full — gis returned as many rows as requested (limit, default 40, max 350) — so more listings likely exist; raise limit or narrow with price/beds filters. ZIP queries that fall into Redfin's cross-continent fallback (e.g. ZIP 28746 returning Seattle results) now error loudly. Only for_sale status is supported; sold / for_rent return an error (use redfin_get_comparable_rentals for rentals, redfin_get_market_report for sold-price trends). Read-only; safe to call repeatedly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax listings to return (default 40; values above 350, the gis hard cap, are clamped to 350).
boundsNoOptional lat/lng box: search this drawn-map area instead of the resolved region (works inside big cities where ZIP/neighborhood regions fall back). `location` is then only a label.
statusNoListing status. Only for_sale is supported; sold and for_rent return an error rather than for-sale results.
beds_minNo
locationYesFree-text location: city, ZIP, neighborhood, or address (e.g. "Brooklyn, NY", "94110", "Park Slope")
baths_minNo
price_maxNo
price_minNo
home_typesNoRestrict to one or more property types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / bounds
      Added value: +{
+  "description": "Optional lat/lng box: search this drawn-map area instead of the resolved region (works inside big cities where ZIP/neighborhood regions fall back). `location` is then only a label.",
+  "properties": {
+    "east": {
+      "type": "number"
+    },
+    "north": {
+      "type": "number"
+    },
+    "south": {
+      "type": "number"
+    },
+    "west": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "north",
+    "south",
+    "east",
+    "west"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changedv1.1.2
    • changedInput schema / properties / limit / description
      Previous value: -"Max listings to return (default 40)."New value: +"Max listings to return (default 40; values above 350, the gis hard cap, are clamped to 350)."
    • changedInput schema / properties / status / description
      Previous value: -"Listing status. Only for_sale fully works in v0.1.0."New value: +"Listing status. Only for_sale is supported; sold and for_rent return an error rather than for-sale results."
  3. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv0.10.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, openWorld), and the description adds substantial behavior beyond them: coverage codes and their meaning, result_cap_hit semantics, limit clamping, and the loud error on ZIP cross-continent fallback. This is rich operational context not derivable from structured fields.

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?

Purpose is front-loaded in the first sentence and each sentence carries operational value (coverage, cap, fallback, status). It is dense and long, but the density is justified; only mild trimming is possible.

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

Completeness5/5

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

No output schema, yet the description enumerates returned fields (price, beds/baths, sqft, year built, address, URL) and decodes resolved_as/coverage/result_cap_hit. An agent has everything needed to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 56%, and the description compensates for the key params — limit default/max behavior, bounds overriding the resolved region, status enum restriction, and accepted location formats. Beds/baths/price/home_types are left as 'optional filters' without added meaning, a minor gap.

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?

Specific verb+resource ('Search Redfin listings by location...and optional filters') with explicit scope, and it distinguishes itself from siblings by naming redfin_get_by_address, redfin_get_comparable_rentals, and redfin_get_market_report. The agent knows exactly what this does versus the alternatives.

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

Usage Guidelines5/5

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

Explicit when-to-use for bounds (drawn-map area in big cities), for address short-circuit, for profile_only coverage (use per-property lookup), and for status restrictions (rentals/sold routed to named siblings). Conditions that select alternatives are stated directly.

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