Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

redfin_property

Fetch Redfin public property details using a listing URL or property_id. Add listing_id with property_id for more complete data.

Instructions

Get Redfin property. Returns Redfin public property details. Provide a listing url, or a property_id (optionally with listing_id).

Input Schema

NameRequiredDescriptionDefault
urlNoRedfin listing URL (primary key)
listing_idNoRedfin listing id, improves completeness with property_id
property_idNoRedfin property id, used when url is not provided

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. Beyond noting the data is 'public', it discloses nothing about auth, rate limits, error behavior, or completeness of the returned record, which is thin for a fetch tool with zero annotation coverage.

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, front-loaded with the purpose and then the identifier rules. Minor redundancy between 'Get Redfin property' and 'Returns Redfin public property details', but nothing wasteful.

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 simple lookup tool with no output schema and no annotations, the description covers the essentials (what it returns, how to identify the property) but omits return structure and failure modes. Adequate, 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 coverage is 100%, so the schema already documents all three parameters. The description adds the precedence rule (url as primary vs property_id) and the listing_id pairing, which slightly exceeds the schema's isolated field descriptions, but the schema does the heavy lifting.

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 ('Get Redfin property') and clarifies the return ('Redfin public property details'). It does not differentiate from closely related siblings like redfin_search, redfin_estimate, or redfin_similar, so an agent must infer the boundary itself.

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 description gives identifier routing (url first, else property_id, optionally listing_id), which is useful invocation guidance. However, it offers no when-to-use/when-not guidance relative to alternatives such as redfin_search, leaving the selection context 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