Crawlora MCP

streeteasy_sales_search

Read-only

Search StreetEasy sale listings by area, status, sale type, price, rooms, maintenance, taxes, price per square foot, year built, prewar, development, income restriction, school, ZIP, keywords, building type, amenities, pets, open house, tours, transit, and sort. Status accepts active, preview, coming_soon, in_contract, sold, or unavailable; omitted status defaults to active, preview, and coming_soon. Sale type accepts sponsor_unit, foreclosure, resale, or restricted_sale. Use streeteasy_areas to find valid location IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area_id": "<area_id>"
    },
    "name": "streeteasy_sales_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based result page. Defaults to 1.
`sort`	No	Result order. Allowed values: default, newest, recently_updated, price_desc, price_asc, largest, smallest.
`prewar`	No	Set true to select prewar buildings.
`amenity`	No	Amenities: washer_dryer, dishwasher, private_outdoor_space, central_air, furnished, fireplace, loft, city_view, garden_view, park_view, skyline_view, water_view, elevator, doorman, laundry, gym, parking, shared_outdoor_space, pool, pied_a_terre, childrens_playroom, smoke_free, storage.
`area_id`	Yes	Required. StreetEasy area IDs from streeteasy_areas; repeat for multiple areas.
`tour_3d`	No	Require a 3D tour.
`keywords`	No	StreetEasy listing-description keyword filter.
`max_sqft`	No	Maximum square footage.
`min_sqft`	No	Minimum square footage. UI presets are 500, 600, 700, 800, 900, 1000, 1250, 1500, 2000, 2500, 3000, 3500, 4000, and 5000 or more.
`per_page`	No	Results per page, 1-500. Defaults to 500.
`zip_code`	No	Five-digit ZIP code.
`max_price`	No	Maximum sale price. StreetEasy UI presets range from 100000 through 30000000.
`min_price`	No	Minimum sale price. StreetEasy UI presets range from 100000 through 30000000.
`sale_type`	No	Sale types visible in StreetEasy filters: sponsor_unit, foreclosure, resale, restricted_sale. Repeat for multiple.
`school_id`	No	StreetEasy school IDs selected by its public sale-search school filter; repeat for multiple schools.
`open_house`	No	Require an open house within the next seven days.
`video_tour`	No	Require a video tour.
`development`	No	New development filter. Verified value: pre_construction.
`sale_status`	No	Sale listing statuses: active, preview, coming_soon, in_contract, sold, unavailable. Repeat for multiple. Defaults to active, preview, and coming_soon.
`max_bedrooms`	No	Maximum bedroom count; 0 means Studio and 4 means 4 or more.
`min_bedrooms`	No	Minimum bedroom count; 0 means Studio and 4 means 4 or more.
`pets_allowed`	No	Require listings that allow pets.
`transit_line`	No	Transit lines: 1, 2, 3, 4, 5, 6, 7, A, C, E, B, D, F, M, G, N, Q, R, W, J, Z, L, S, HBLR, PATH.
`building_type`	No	Building types: condo, co-op, house, multifamily.
`max_bathrooms`	No	Maximum bathroom count.
`min_bathrooms`	No	Minimum bathroom count. UI presets are 1, 1.5, 2, and 3 or more.
`max_year_built`	No	Maximum building year built.
`min_year_built`	No	Minimum building year built.
`max_maintenance`	No	Maximum monthly maintenance fee.
`min_maintenance`	No	Minimum monthly maintenance fee.
`optional_amenity`	No	Nice-to-have amenities; these are preferred but not required. Accepts the same values as amenity.
`income_restricted`	No	Set true to select income-restricted homes.
`max_monthly_taxes`	No	Maximum monthly property taxes.
`min_monthly_taxes`	No	Minimum monthly property taxes.
`max_price_per_sqft`	No	Maximum price per square foot.
`min_price_per_sqft`	No	Minimum price per square foot.
`include_unknown_price_per_sqft`	No	Include listings with unknown price per square foot.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / amenity / items / description

Added value: +"Documented values: washer_dryer, dishwasher, private_outdoor_space, central_air, furnished, fireplace, loft, city_view, garden_view, park_view, skyline_view, water_view, elevator, doorman, laundry, gym, parking, shared_outdoor_space, pool, pied_a_terre, childrens_playroom, smoke_free, storage."

addedInput schema / properties / building_type / items / description

Added value: +"Documented values: condo, co-op, house, multifamily."

addedInput schema / properties / optional_amenity / items / description

Added value: +"Documented values: washer_dryer, dishwasher, private_outdoor_space, central_air, furnished, fireplace, loft, city_view, garden_view, park_view, skyline_view, water_view, elevator, doorman, laundry, gym, parking, shared_outdoor_space, pool, pied_a_terre, childrens_playroom, smoke_free, storage."

addedInput schema / properties / sale_status / items / description

Added value: +"Documented values: active, preview, coming_soon, in_contract, sold, unavailable."

addedInput schema / properties / sale_type / items / description

Added value: +"Documented values: sponsor_unit, foreclosure, resale, restricted_sale."

addedInput schema / properties / transit_line / items / description

Added value: +"Documented values: 1, 2, 3, 4, 5, 6, 7, A, C, E, B, D, F, M, G, N, Q, R, W, J, Z, L, S, HBLR, PATH."

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond the schema: the default status set ('omitted status defaults to active, preview, and coming_soon'). It does not cover pagination behavior or rate limits, and per_page default of 500 is only in the schema.

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

Conciseness3/5

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

The first sentence is a long laundry list of filter dimensions that reads as filler since the schema enumerates them anyway. The genuinely useful facts (status default, sale type values, area_id guidance) are present but buried after the list rather than front-loaded.

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 37-parameter search tool with full schema coverage and an output schema, the description is largely complete: it flags the required parameter, the source for valid IDs, and the important status-default behavior. Minor gaps such as pagination semantics exist but are covered by the 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 coverage is 100%, so the schema already documents all 37 parameters thoroughly, and an output schema exists. The description adds the crucial status-default behavior, but mostly restates the filter dimensions the schema already lists. Baseline 3 is appropriate when structured fields do the heavy lifting.

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?

States a specific verb+resource: 'Search StreetEasy sale listings' and enumerates the dimensions of the search. It is clearly distinguished from sibling streeteasy_rentals_search and streeteasy_quick_search without ambiguity.

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 tells the agent that area_id is required and to get valid location IDs from streeteasy_areas, which is useful routing. However it never states when to prefer this tool over streeteasy_rentals_search or quick_search, and no exclusions are given.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.