Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_areas

List StreetEasy search areas across NYC and NJ, including boroughs, neighborhoods, and sub-neighborhoods, to find area IDs for rental searches.

Instructions

List StreetEasy search areas. Lists StreetEasy's search area hierarchy: NYC and NJ roots, boroughs, neighborhoods and sub-neighborhoods. Each area has an id, parentId, level, name and short name. Use an id as a repeated area_id in /streeteasy/rentals/search. The list was 349 options on 2026-09-29 and can change.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 largely delivers: it declares this is a read-only enumeration, enumerates the returned fields (id, parentId, level, name, short), and flags volatility ('349 options... can change'). It doesn't discuss caching or auth, but the staleness warning is valuable behavior context.

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?

Four tight sentences, front-loaded with the action and scope, then field structure, then the concrete downstream usage. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description properly compensates by naming the returned fields and the hierarchy shape, and it ties the result to the consumer tool. For a parameterless static list this is complete.

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?

The tool takes zero parameters, so the baseline is 4. Nothing to mis-specify, and the description correctly implies no filtering/inputs are accepted.

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 and resource ('List StreetEasy search areas') and immediately delimits the scope (NYC/NJ roots, boroughs, neighborhoods, sub-neighborhoods). An agent can distinguish it from streeteasy_rentals_search, streeteasy_building, and streeteasy_unit without opening a 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 states the downstream usage: take an `id` and pass it as a repeated `area_id` in /streeteasy/rentals/search. That gives clear context for when to call it, though it doesn't name an alternative lookup tool or state exclusions.

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