Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

redfin_search

Read-onlyIdempotent

Retrieve parsed property listings from a Redfin search URL, including address, price, beds/baths, square footage, and URL. Build datasets of matching properties for analysis.

Instructions

Retrieve parsed Redfin search results for a search-results URL.

    Returns a structured list of properties — address, price, beds/baths,
    square footage, URL — from a Redfin search-results page (with its filters
    encoded in the URL).

    When to use:
    - Collecting listings for an area or filter set from a Redfin search URL
    - Building datasets of properties matching search criteria

    When NOT to use:
    - A single property (use 'redfin_for_sale' / 'redfin_for_rent')

    Args:
        params (RedfinSearchParams): url (required, full Redfin search URL with
            filters) plus optional tld, country_code, and output_format.

    Returns:
        str: JSON (default) or CSV containing the structured search results.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already indicate safety. Description adds return format details and potential errors (API key, rate limit, request failure), which are consistent with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-organized with clear sections, no redundancy, and every sentence adds value. Efficient use of space.

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?

Given the tool's complexity (single parameter with nested sub-params, output schema exists, annotations present), the description covers purpose, usage, parameters, return type, and errors comprehensively.

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 description coverage is 0%, so description must compensate. It lists all four parameters (url, tld, country_code, output_format) and explains url is required and must be a search-results URL, adding meaning beyond the schema.

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?

The description clearly states the verb 'Retrieve parsed Redfin search results' and specifies the resource 'for a search-results URL'. It distinguishes from sibling tools like redfin_for_sale and redfin_for_rent by explicitly noting when not to use them.

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?

Includes explicit 'When to use' and 'When NOT to use' sections, with specific mention of alternative tools (redfin_for_sale, redfin_for_rent). Provides clear context for appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scraperapi/scraperapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server