Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

redfin_for_sale

Read-onlyIdempotent

Retrieve structured property data—price, beds, baths, square footage, photos, and price history—from any Redfin for-sale listing by providing its URL.

Instructions

Retrieve parsed Redfin listing data for a home for sale.

    Returns structured property data — price, beds/baths, square footage,
    address, description, photos, price history, and listing details — from a
    Redfin for-sale property page.

    When to use:
    - Extracting details for a specific for-sale property from its Redfin URL
    - Real-estate data collection, comps, or listing monitoring

    When NOT to use:
    - A rental listing (use 'redfin_for_rent')
    - A search-results page (use 'redfin_search') or agent profile ('redfin_agent')

    Args:
        params (RedfinForSaleParams): url (required, full Redfin property URL)
            plus optional raw, tld, country_code, and output_format.

    Returns:
        str: JSON (default) or CSV containing the structured property data.

    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 already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by noting error conditions (missing API key, rate limit, request failure) and the output format, but does not mention caching or internal state changes, which are already covered by idempotency.

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?

The description is concise, structured with clear sections (When to use, When NOT to use, Args, Returns, Raises). Every sentence adds value, and there is no redundancy or fluff.

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 existence of an output schema, the description adequately covers the return value. The tool is simple (one required param) and annotations cover safety. The description provides all necessary behavioral context beyond structured fields.

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?

All parameters are well-described in the input schema (100% coverage). The description only lists the parameters without adding new meaning, so it meets the baseline of 3. It does not provide extra context 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 uses a specific verb 'Retrieve' and identifies the resource as 'parsed Redfin listing data for a home for sale'. It also lists the data fields (price, beds/baths, etc.) and distinguishes from siblings redfin_for_rent, redfin_search, and redfin_agent.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance, naming alternative tools for rentals, search results, and agent profiles. The description helps the agent decide when to invoke this tool over siblings.

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