Crawlora MCP

streeteasy_rentals_search

Read-only

Search active StreetEasy rental listings by area, price, rooms, building type, must-have or preferred amenities, pets, open house, tours, transit, and sort. 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_rentals_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based result page. Defaults to 1.
`sort`	No	Result order: default, newest, recently_updated, price_desc, price_asc, largest, smallest.
`amenity`	No	Required amenities; see the complete enum in the endpoint documentation.
`area_id`	Yes	Required. StreetEasy area IDs from streeteasy_areas; repeat for multiple areas.
`tour_3d`	No	Require a 3D tour.
`max_sqft`	No	Maximum square footage.
`min_sqft`	No	Minimum square footage. Visible presets range from 500 to 5000 or more.
`per_page`	No	Results per page, 1-500. Defaults to 500.
`max_price`	No	Maximum monthly rent.
`min_price`	No	Minimum monthly rent.
`open_house`	No	Require an open house within the next seven days.
`video_tour`	No	Require a video tour.
`max_bedrooms`	No	Maximum bedrooms.
`min_bedrooms`	No	Minimum bedrooms; 0 means studio and 4 means 4 or more.
`pets_allowed`	No	Require listings that allow pets.
`transit_line`	No	Nearby transit lines; see the complete enum in the endpoint documentation.
`building_type`	No	Building types: rental, condo, co-op, house, multifamily.
`max_bathrooms`	No	Maximum bathrooms.
`min_bathrooms`	No	Minimum bathrooms. Visible presets are 1, 1.5, 2, and 3 or more.
`optional_amenity`	No	Preferred amenities; results may omit these. Accepts the same values as amenity.

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.

Changed4 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: rental, 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 / 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 5, 2026

TDQS

A4/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 the agent knows this is a safe external read. The description adds the 'active listings' scope constraint, but says nothing about pagination limits or result volume beyond what the schema shows.

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?

Two compact sentences, with the core purpose front-loaded and the helper-tool pointer second. 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?

Given an output schema exists and the input schema is fully documented, the description covers what an agent needs to call it: purpose, facets, and location-ID sourcing. Minor gap is no indication of result caps or how it differs from streeteasy_quick_search.

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% across all 20 parameters, so the schema already documents each filter, its enum values, and defaults. The description only restates the filter categories at a high level, adding no syntax or semantic detail.

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 ('Search') and resource ('active StreetEasy rental listings') plus the full facet set. The adjective 'rental' cleanly separates it from streeteasy_sales_search, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the helper tool streeteasy_areas for obtaining valid area IDs, which is a useful prerequisite. However, it gives no when-not guidance or comparison against siblings such as streeteasy_quick_search.

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.

Resources

Need Help?