Skip to main content
Glama
chrischall

redfin-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get my saved Redfin searches

redfin_get_saved_searches
Read-onlyIdempotent

Retrieve a signed-in user's saved Redfin searches, including count and each search's URL, region, and display text, to list or inspect saved property searches. Read-only and safe to call repeatedly.

Instructions

The signed-in user's saved searches on redfin.com, derived from the saved-searches page HTML. Returns { count, searches }; each entry is { url, region_segment, display_text }. Requires the user to be signed in. When none are found, searches is empty and a note explains it may be no saved searches or a page-scrape miss. Read-only; safe to call repeatedly.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Redfin's payload untouched. No field projection: this server has no verified record of which Redfin fields matter, and inventing one would risk dropping a field a caller needs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed1 schema field changedv0.13.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Redfin's payload untouched. No field projection: this server has no verified record of which Redfin fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.10.1

TDQS

A4.2/5.0
Behavior5/5

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

With annotations already declaring readOnlyHint, idempotentHint and openWorldHint, the description adds genuinely non-derivable context: the data comes from scraping page HTML, so an empty `searches` plus a `note` may mean a scrape miss rather than truly no saved searches. It also states the sign-in requirement and the return contract.

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?

Four compact sentences, front-loaded with what the tool returns and the auth prerequisite. Every sentence carries information; only the trailing "Read-only; safe to call repeatedly" is partly redundant with the annotations.

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?

With no output schema, the description carries the return contract itself (`{ count, searches }` with per-entry `{ url, region_segment, display_text }`) plus the empty-result caveat and auth requirement. An agent has everything needed to call and interpret the result.

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 the single `view` enum is documented in exhaustive detail in the schema itself. The description adds nothing about parameter behavior, so the baseline 3 is appropriate.

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?

States a specific verb+resource and scope: "The signed-in user's saved searches on redfin.com". The qualifier "saved searches" cleanly distinguishes it from the sibling redfin_get_saved_homes, and the note that data is derived from the saved-searches page HTML pins down exactly what is being fetched.

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?

Usage is implied rather than stated: the description tells the agent it "Requires the user to be signed in" and is idempotent, which frames when it is callable, but it never names an alternative (e.g. redfin_get_saved_homes) or explicitly contrasts the two. No when-not-to-use guidance.

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