redfin-mcp-server
Server Details
Single-property deep-dive: history, price/sqft, days-on-market, comps from a Redfin URL.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 2 of 2 tools scored.
The two tools are completely distinct: one searches for properties, the other retrieves detailed information on a specific listing. There is no functional overlap, and an agent can easily differentiate them.
Both tools use a clear verb_noun pattern: 'search_properties' and 'get_property_details'. The naming is consistent and predictable, making it easy to understand each tool's purpose at a glance.
With only 2 tools, the server feels minimal. While it covers basic search and details, the low count suggests limited scope. It could benefit from additional tools like property comparison or photo retrieval, but the current number is just barely sufficient for a simple query scenario.
The tool set covers the core workflow of searching for properties and then retrieving full details. However, it lacks features like favoriting properties, getting market trends, or advanced filtering. For a read-only data retrieval server, it is mostly complete but has minor gaps.
Available Tools
2 toolsget_property_detailsARead-onlyInspect
Retrieve full property details from Redfin listing page. Returns listing description, tax history, HOA fees, property tax amount, nearby schools with ratings, neighborhood safety metrics, walkability scores, and photo gallery/tour URLs. Use for due diligence before making offers or detailed investment analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Redfin property listing URL (e.g. 'https://www.redfin.com/WA/Seattle/123-Main-St-98101') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by listing what is returned (tax history, HOA fees, etc.), but does not mention potential rate limits or other behavioral quirks.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first states action and source, second lists returns and intended use. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given only one parameter with full schema and no output schema, the description sufficiently covers what the tool does and when to use it. No gaps for this complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100% and already describes the URL parameter with an example. The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Retrieve' and identifies the resource as 'full property details from Redfin listing page', clearly distinguishing it from sibling tool 'search_properties'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Use for due diligence before making offers or detailed investment analysis', providing clear context for when to use. However, it does not explicitly exclude alternatives or state when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_propertiesARead-onlyInspect
Query Redfin real estate listings by location and filters for residential properties. Returns asking price, street address, bedrooms, bathrooms, square footage, property type, HOA status, and listing age. Use for home shopping, market analysis, investment research, or neighborhood comparison.
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes | Property location by city, zip code, or full address (e.g. 'Seattle, WA', '98101', '1600 Pennsylvania Ave') | |
| max_price | No | Maximum asking price filter in USD (e.g. 1000000) | |
| min_price | No | Minimum asking price filter in USD (e.g. 300000) | |
| property_type | No | Property category to filter (e.g. 'house', 'condo', 'townhouse', 'multi-family', 'land') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description mentions read-only querying and returned data, consistent with annotations. But lacks disclosure of limitations like rate limits or pagination, which are not covered by annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise sentences covering purpose, data fields, and use cases. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Enumerates return fields, compensating for missing output schema. However, lacks details on pagination, result limits, or sorting.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all parameters with descriptions. The description repeats 'location and filters' without adding semantic details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the tool queries Redfin listings with location and filters, returns specific fields, and lists use cases. It distinguishes from sibling 'get_property_details' by focusing on search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides use cases but no explicit guidance on when not to use or comparison to sibling tool for detailed property info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!