Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_housing_markets_item

Fetch a U.S. housing market record by region type and Redfin table ID, or request the full monthly history series for national, metro, county, city, or ZIP trends.

Instructions

Get a US housing market record from the dataset. Returns one housing-market record by region_type and Redfin table_id from dataset id enum value housing-markets. 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 (defaults to All Residential). period defaults to the most recent period on record. Pass history=true to get the full monthly series (a {dataset, region_type, table_id, property_type, items} envelope, sorted by period ascending) instead of a single record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoExact period start date, YYYY-MM-DD; defaults to the latest period
historyNoReturn the full monthly series instead of a single period
table_idYesRedfin table id (the region's stable numeric id)
region_typeYesRegion level enum: national, metro, county, city, zip
property_typeNoProperty type enum: All Residential, Single Family Residential, Condo/Co-op, Townhouse, Multi-Family (2-4 Unit), Single Units Only; defaults to All Residential

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / region_type / enum
      Added value: +[
+  "national",
+  "metro",
+  "county",
+  "city",
+  "zip"
+]
  2. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does well by explaining default behavior for `period`, the property_type default, and the exact envelope structure when `history=true`, including sorting order. It does not cover error cases or rate limits, but for a simple getter this is a solid disclosure.

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 dense but every sentence earns its place: purpose, key identifiers, enum values, defaults, and the history-mode behavior. It is front-loaded with the core purpose and then organized by parameter behavior, with no filler.

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?

For a 5-parameter tool with no output schema, the description covers the required identifiers, optional parameters, defaults, and the history response envelope. It does not enumerate the fields inside a single record, but the description is still sufficient for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description adds meaning beyond the schema by specifying the dataset enum value, clarifying defaults for `period` and `property_type`, and describing the history response shape. This extra context helps the agent invoke parameters correctly.

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 a specific verb and resource: 'Get a US housing market record from the dataset' and identifies the exact record keyed by region_type and Redfin table_id. It also names the dataset enum value `housing-markets`, which distinguishes this item-level tool from its dataset search/facets siblings.

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 implies usage context: call this when you have a known region_type and table_id and want a single record or full history. However, it does not explicitly mention alternatives like datasets_housing_markets_search or datasets_housing_markets_facets, nor when not to use this tool.

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