Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

streeteasy_quick_search

Search StreetEasy's public quick-search page with a free-text query to return rendered neighborhood, building, complex, school, agent, and recorded-sale results in one JSON response.

Instructions

Search StreetEasy across public result types. Searches StreetEasy's public quick-search page and returns its rendered neighborhood, building, complex, school, agent, and recorded-sale groups. Recorded-sale entries are a limited anonymous preview when the page requires registration to see the remaining matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text StreetEasy quick-search query (1-160 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.2/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 behavioral burden. It usefully discloses that recorded-sale entries are a limited anonymous preview requiring registration for the remaining matches, which is meaningful partial-result context. However, it does not cover rate limits, pagination, or auth expectations for the rest of the result types, so it is only partially transparent.

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?

Three sentences, front-loaded with the core action and scope, followed by return groups and a caveat. There is mild redundancy in restating 'Searches StreetEasy' twice, but no wasted padding overall.

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 one-parameter tool with no annotations and no output schema, the description compensates by naming the result groups it returns and flagging the registration-gated partial results. This covers what an agent needs to call it and interpret the output, though it omits any sibling routing guidance.

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% and there is a single query parameter already documented with its length constraint. The description adds no format, syntax, or example guidance for the query beyond what the schema provides, so the baseline of 3 applies.

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?

The description states a specific verb ('Search') and resource (StreetEasy's public quick-search page) and enumerates the returned result groups (neighborhood, building, complex, school, agent, recorded-sale). This clearly separates it from a narrow endpoint. It does not explicitly contrast with siblings like streeteasy_rentals_search or streeteasy_sales_search, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. The agent must infer that this is a general keyword lookup as opposed to the structured rentals_search or sales_search siblings. The only implicit hint is 'public quick-search page' and 'across public result types'.

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