Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_housing_markets_search

Search monthly Redfin housing market statistics per US region and property type since 2012, with affordability metrics from Census ACS. Filter by price, inventory, days on market, and more.

Instructions

Search the US housing markets dataset. Searches monthly Redfin housing-market statistics per region and property type since 2012, joined to Census ACS income for affordability metrics. region_type enum: national, metro, county, city, zip. property_type enum: All Residential, Single Family Residential, Condo/Co-op, Townhouse, Multi-Family (2-4 Unit), Single Units Only. Sort enum: relevance, price_desc, price_asc, list_price_desc, list_price_asc, price_to_income_desc, price_to_income_asc, salary_to_buy_desc, salary_to_buy_asc, dom_asc, dom_desc, inventory_desc, homes_sold_desc, period_desc. Use latest=true for the most recent period per region series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over region name and city, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, price_desc, price_asc, list_price_desc, list_price_asc, price_to_income_desc, price_to_income_asc, salary_to_buy_desc, salary_to_buy_asc, dom_asc, dom_desc, inventory_desc, homes_sold_desc, period_desc
latestNoFilter for the most recent period per region and property type
periodNoExact period start date filter, YYYY-MM-DD
zip_codeNoExact zip code filter (zip-level rows only), e.g. 60616
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
state_codeNoExact two-letter state code filter, e.g. CA
region_typeNoRegion level enum: national, metro, county, city, zip
max_inventoryNoMaximum active inventory
min_inventoryNoMinimum active inventory
property_typeNoProperty type enum: All Residential, Single Family Residential, Condo/Co-op, Townhouse, Multi-Family (2-4 Unit), Single Units Only
max_median_domNoMaximum median days on market
min_homes_soldNoMinimum homes sold in the period
min_median_domNoMinimum median days on market
max_salary_to_buyNoMaximum salary needed to buy in USD per year
min_salary_to_buyNoMinimum salary needed to buy in USD per year
parent_metro_codeNoExact parent metro (CBSA) code filter, e.g. 16980
max_price_to_incomeNoMaximum price-to-income ratio
min_price_to_incomeNoMinimum price-to-income ratio
max_median_list_priceNoMaximum median list price in USD
max_median_sale_priceNoMaximum median sale price in USD
min_median_list_priceNoMinimum median list price in USD
min_median_sale_priceNoMinimum median sale price in USD
Behavior3/5

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

No annotations provided, so description must carry burden. It mentions data source, time range, and a usage tip for latest=true, but lacks details on pagination behavior, rate limits, return format, or destructive potential. The tool is read-only, but this is not explicitly stated.

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 (5-6 sentences) and front-loaded with purpose, data source, and key enums. No superfluous content.

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?

No output schema, so description should explain response contents. It mentions data sources but not specific fields, pagination, or result structure. The schema's many filter parameters partially compensate by implying output includes those fields.

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 coverage is 100%, baseline 3. The description adds value by explaining the joined datasets (affordability metrics) and providing a concrete usage tip for latest=true. However, enum lists largely duplicate schema descriptions.

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 tool searches the US housing markets dataset, specifies data sources (Redfin + Census ACS), lists key enums, and distinguishes from sibling tools like datasets_housing_markets_facets and datasets_housing_markets_item by focusing on search functionality.

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 explains what the tool does but does not explicitly state when to use it versus alternatives like facets or item tools. It implies search use case but lacks explicit guidance or exclusions.

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/Crawlora-org/crawlora-mcp'

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