Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

redfin_for_rent

Read-onlyIdempotent

Get structured rental data from a Redfin property page: rent, beds, baths, square footage, address, description, photos, and availability.

Instructions

Retrieve parsed Redfin listing data for a rental property.

    Returns structured rental data — rent, beds/baths, square footage, address,
    description, photos, and availability — from a Redfin rental property page.

    When to use:
    - Extracting details for a specific rental from its Redfin URL
    - Rental-market data collection or listing monitoring

    When NOT to use:
    - A for-sale listing (use 'redfin_for_sale')
    - A search-results page (use 'redfin_search') or agent profile ('redfin_agent')

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

    Returns:
        str: JSON (default) or CSV containing the structured rental 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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds error conditions (ToolError for missing API key, rate limit exceeded, request failure). Does not contradict annotations. No further behavioral context needed.

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-structured with clear sections (purpose, when to use/not use, args, returns, raises). Front-loaded with main action. Every sentence adds value without redundancy.

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?

Tool is a data retrieval endpoint with output schema and annotations. Description covers use cases, parameter summary, and error raising. Minor gap: rate limit details could be more explicit, but overall 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 descriptions cover all parameters (100% coverage), so baseline is 3. Description merely summarizes the parameters (url required, others optional) without adding new 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?

Description clearly states 'Retrieve parsed Redfin listing data for a rental property' with specific verb and resource. Lists returned fields and distinguishes from siblings by explicitly naming redfin_for_sale, 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?

Includes explicit 'When to use' and 'When NOT to use' sections with specific use cases and alternative tool names, providing excellent guidance for selection.

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