Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zillow_autocomplete

Find Zillow location candidates by query and search context. Returns region IDs and types for sale, rent, or sold searches; map bounds are not included.

Instructions

Autocomplete Zillow locations. Returns Zillow autocomplete candidates, including region ids and types. Zillow autocomplete does not currently return map bounds.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, clamped to 20
queryYesLocation query
statusNoSearch context. Allowed values: for_sale (aliases sale, for-sale), for_rent (aliases rent, for-rent), sold

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

B3.4/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 results include region IDs and types and that map bounds are not currently returned, but it omits other behavioral details such as result ordering, pagination behavior, or whether limit is applied before or after filtering.

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 three short sentences with no wasted text. Purpose is front-loaded, followed by return content and a relevant limitation.

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 simple three-parameter autocomplete tool with fully documented inputs, the description covers purpose, return content, and a notable missing field. It does not need an output schema explanation because it already names the key returned fields, though fuller result-shape detail would improve completeness.

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 input schema already documents query, limit, and status with enum aliases. The description does not add meaning beyond the schema, which is acceptable at the baseline for fully documented parameters.

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 and resource: 'Autocomplete Zillow locations.' It also clarifies the return content, naming region IDs and types. It does not explicitly contrast itself with sibling tools like zillow_search or zillow_property, so it stops 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?

The description does not say when to use this tool versus alternatives such as zillow_search or zillow_property. Usage is only implied by the word 'autocomplete,' with no explicit when/when-not guidance.

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