Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_unit

Fetch a StreetEasy unit's structured listing details—address, price, description, amenities, and open houses—using its building slug and unit path.

Instructions

Get StreetEasy unit details. Retrieves a public unit's structured listing details from its server-rendered page, including address, asking price, description, amenities, and scheduled open houses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitYesStreetEasy unit segment from /building/{building_slug}/{unit}
building_slugYesStreetEasy building slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that data comes from a 'server-rendered page' for a 'public unit' and lists what is returned, but omits auth/permission needs, failure modes for invalid slugs, and any rate-limit or caching behavior.

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 tightly written sentences, front-loaded with the purpose and followed by the return scope. No filler and nothing redundant with the schema.

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?

With no output schema and no annotations, the description compensates reasonably by enumerating the returned fields and noting the public/server-rendered nature. Missing pieces like auth requirements or error behavior keep it from a 5, but it covers what an agent needs to call it.

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 both building_slug and unit are already documented in the schema, including the fact that 'unit' derives from the /building/{building_slug}/{unit} URL path. The description adds no extra format or syntax guidance beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get StreetEasy unit details') and enumerates the returned fields (address, asking price, description, amenities, open houses). This clearly distinguishes it from streeteasy_building and the search tools, though it doesn't explicitly name a sibling for contrast.

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?

Usage is implied: fetch one unit given a building_slug and unit segment. There is no explicit when-to-use, when-not, or named alternative (e.g., streeteasy_building for building-level data, or streeteasy_rentals_search for discovering units), so the agent must infer routing.

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