Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zillow_search

Search Zillow listings by location, map bounds, or region ID to get normalized public listing results.

Instructions

Search Zillow listings. Returns normalized Zillow public listing search results. Callers must pass complete map bounds from autocomplete when available, or a region id fallback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eastNoMap east bound from autocomplete
pageNo1-based page
westNoMap west bound from autocomplete
northNoMap north bound from autocomplete
southNoMap south bound from autocomplete
statusNoSearch context. Allowed values: for_sale (aliases sale, for-sale), for_rent (aliases rent, for-rent), sold
locationYesDisplay location
region_idNoZillow region id from autocomplete, used when complete bounds are not provided
region_typeNoZillow region type from autocomplete, used with region_id fallback

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / status / enum
      Added value: +[
+  "for_sale",
+  "sale",
+  "for-sale",
+  "for_rent",
+  "rent",
+  "for-rent",
+  "sold"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"Search context: for_sale, for_rent, or sold"New value: +"Search context. Allowed values: for_sale (aliases sale, for-sale), for_rent (aliases rent, for-rent), sold"
  3. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context by saying results are normalized and requiring bounds/region id, but it does not address read-only safety, pagination behavior, or potential failure modes. This is adequate but not thorough.

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?

The description is two sentences with no filler. It front-loads the purpose and then gives the essential calling requirement, which is appropriately sized for the tool.

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

Completeness3/5

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

The schema already documents all 9 parameters, and the description captures the central geolocation requirement. However, with no annotations and no output schema, it leaves gaps such as default status, page behavior, and what happens if only location is provided. It is adequate but not fully complete.

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 bounds-or-region-id instruction mostly restates what the schema already says for region_id and the bound parameters, adding emphasis rather than new semantic detail.

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 clearly states a specific verb ('Search') and resource ('Zillow listings') and mentions that it returns normalized public listing search results. This distinguishes it from sibling zillow_property, though it does not explicitly name the alternative.

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?

It provides a clear condition: callers must pass complete map bounds from autocomplete when available, or fall back to a region id. This gives practical guidance on how to invoke the tool, though it does not discuss when to choose a sibling tool instead.

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