Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

redfin_similar

Retrieve Redfin comparable listings for a property using its property_id to compare nearby homes by price, beds, baths, square footage, and days on market.

Instructions

Get Redfin comparable listings. Returns the comparable listings Redfin shows for a property, identified by the required property_id. Each row has the address, city, state, zip, price, beds, baths, sqft, price_per_sqft, days on market, MLS number, hoa_monthly, lot size, year built, status, image and URL, plus coordinates when present.

Input Schema

NameRequiredDescriptionDefault
property_idYesRedfin property id

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden. It discloses the returned row fields (address through coordinates), which is genuine behavioral context, but says nothing about permissions, rate limits, pagination, or whether results can be empty. It adds output detail but no operational behavior.

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?

Two sentences, purpose front-loaded first, then a field enumeration. The field list is long but earns its place because there is no output schema; nothing is wasted on filler.

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 simple one-parameter read tool with no output schema, the description compensates well by enumerating the return fields. It is nearly complete; the only real gap is the absence of when-to-use context against sibling Redfin tools.

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% for the single parameter, so the schema already documents 'Redfin property id'. The description merely confirms it is required and identifies the target, adding no new meaning beyond the schema. Baseline 3 applies.

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 and resource ('Get Redfin comparable listings') and scopes it precisely to the comparables Redfin shows for a given property. This cleanly distinguishes it from siblings like redfin_property, redfin_search, and redfin_estimate without the agent needing to open schemas.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the other Redfin siblings (redfin_property, redfin_search, redfin_estimate). The description only restates that property_id is required, offering no conditions, prerequisites, or alternatives.

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