Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_sales_search

Search StreetEasy sale listings by area, price, bedrooms, amenities, status, and transit to find properties that match specific buying criteria.

Instructions

Search StreetEasy sale listings. Searches public sale listings with location, status, sale type, price, bedroom, bathroom, square-footage, carrying cost, building age, school, ZIP, keyword, building type, amenity, pet, open-house, virtual-tour, transit, and sort filters. Obtain area IDs from /streeteasy/areas. When sale_status is omitted, active, preview, and coming_soon listings are included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based result page
sortNodefault, newest, recently_updated, price_desc, price_asc, largest, or smallest
prewarNoSet true to select prewar buildings
amenityNoAmenity filter; repeat for multiple
area_idYesStreetEasy area ID from /streeteasy/areas; repeat for multiple areas
tour_3dNoRequire a 3D tour
keywordsNoListing-description keyword filter
max_sqftNoMaximum square footage
min_sqftNoMinimum square footage
per_pageNoResults per page, 1-500
zip_codeNoFive-digit ZIP code
max_priceNoMaximum sale price
min_priceNoMinimum sale price
sale_typeNoSale type; repeat for multiple.
school_idNoStreetEasy school ID selected by the public search UI; repeat for multiple schools
open_houseNoRequire open house within the next seven days
video_tourNoRequire a video tour
developmentNoNew development filter
sale_statusNoSale status; repeat for multiple. Defaults to active, preview, and coming_soon.
max_bedroomsNoMaximum bedrooms
min_bedroomsNoMinimum bedrooms; zero means studio
pets_allowedNoRequire pets allowed
transit_lineNoNearby transit line; repeat for multiple
building_typeNoBuilding type
max_bathroomsNoMaximum bathrooms
min_bathroomsNoMinimum bathrooms
max_year_builtNoMaximum building year built
min_year_builtNoMinimum building year built
max_maintenanceNoMaximum monthly maintenance fee
min_maintenanceNoMinimum monthly maintenance fee
optional_amenityNoNice-to-have amenity; results may omit these. Repeat for multiple.
income_restrictedNoSet true to select income-restricted homes
max_monthly_taxesNoMaximum monthly property taxes
min_monthly_taxesNoMinimum monthly property taxes
max_price_per_sqftNoMaximum price per square foot
min_price_per_sqftNoMinimum price per square foot
include_unknown_price_per_sqftNoInclude listings with unknown price per square foot

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully surfaces the default status set (active, preview, coming_soon) and that results are public listings, but says nothing about pagination defaults, result limits, or rate behavior that an agent planning many calls would want.

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?

Front-loads the purpose and keeps the guidance short. The first two sentences overlap somewhat ('Search StreetEasy sale listings' then 'Searches public sale listings with...'), and the long filter enumeration is dense, but nothing is truly wasted.

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 no output schema, the description covers purpose, the required area_id prerequisite, and the key default status behavior. Return shape and pagination aren't addressed, but that is a minor gap given the rich 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 baseline is 3. The description's filter list and default-status note largely restate what the schema descriptions already state (e.g. 'Defaults to active, preview, and coming_soon' appears in both), adding no syntax or format detail beyond the schema.

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 (StreetEasy sale listings), and the enumerated filter categories reinforce the domain. The 'sale' scope distinguishes it from the sibling streeteasy_rentals_search without requiring the schema to be opened.

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?

Provides a concrete prerequisite ('Obtain area IDs from /streeteasy/areas') and states the default behavior when sale_status is omitted. It stops short of explicitly contrasting this tool with the rentals sibling, but the context is clear enough to select it correctly.

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