Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_housing_markets_search

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.

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / region_type / enum
      Added value: +[
+  "national",
+  "metro",
+  "county",
+  "city",
+  "zip"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "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"
+]
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on cost: it discloses 1 credit per record, a 2-credit minimum, that an empty result still costs 2, and that a full page of 100 costs 100. It also scopes the data (since 2012, joined to ACS income). It omits return-shape and pagination/rate-limit behavior, keeping it out of the top tier.

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

Conciseness4/5

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

The purpose is front-loaded, followed by data scope, enums, the `latest` hint, and billing. It is well organized but the inline enum lists (region_type, property_type, sort) duplicate schema content and add length without new information.

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?

For a 24-parameter search with no output schema and no annotations, the description covers purpose, data scope, and billing adequately. It does not describe the returned record shape, which is the main remaining gap given the absence of an output schema.

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 description coverage is 100%, so the schema already documents all 24 parameters. The description largely restates enum values and the `latest` semantics already present in the schema, adding little beyond baseline meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search the US housing markets dataset') and details the underlying data (monthly Redfin stats joined to Census ACS income for affordability). It is clear, though it does not explicitly distinguish itself from the sibling facets/item tools, so it stops short of a 5.

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?

Usage is largely implied by the name and the data description; there is a targeted hint ('Use `latest=true` for the most recent period per region series') and a billing note that implicitly frames cost. However, there is no explicit when-to-use / when-not guidance and no mention of the sibling facets or item tools, so it is minimum-viable rather than directive.

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

Deploy Server

Other Tools