Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zillow_autocomplete

Resolve Zillow location queries into normalized autocomplete candidates, including region IDs and types, for search, rental, or sold status contexts.

Instructions

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

Input Schema

TableJSON 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.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 behavioral burden. It usefully discloses what the response contains (normalized region ids and types) and a notable limitation (no map bounds), which is real value beyond a bare name. It omits any auth, rate-limit, or pagination context, so it is adequate but not rich.

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 short sentences, front-loaded with the core operation and followed by return contents and a limitation. No padding or repetition; each sentence carries information.

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, single-purpose autocomplete with no output schema, the description describes the return contents (region ids, types) and a key negative (no map bounds), which is what an agent needs. It could go further on usage context, but it is largely complete for this tool's complexity.

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 schema already documents query, limit (clamped to 20), and the status enum with aliases. The description adds no parameter syntax or format detail, so baseline 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?

States a specific verb+resource: 'Autocomplete Zillow locations.' It clearly conveys the operation and returns candidates with region ids and types. It does not explicitly differentiate itself from siblings like zillow_search or zillow_property, but the purpose is unambiguous.

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 gives no when-to-use guidance or alternatives. An agent must infer that this is for resolving location queries to region ids before a zillow_search call. There are no exclusions or routing hints to sibling tools.

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