Crawlora MCP

zillow_search

Read-only

Search Zillow listings by required location, with optional region ID or complete west/east/south/north map bounds and supported listing filters. Use zillow_property to retrieve details for one property identifier.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "zillow_search"
  }
}

Input Schema

Name	Required	Description
`east`	No	East longitude of a map bounding box; pass all of west/east/south/north together. Zillow autocomplete does not currently return map bounds.
`page`	No	Result page, default 1.
`west`	No	West longitude of a map bounding box; pass all of west/east/south/north together. Zillow autocomplete does not currently return map bounds.
`north`	No	North latitude of a map bounding box; pass all of west/east/south/north together. Zillow autocomplete does not currently return map bounds.
`south`	No	South latitude of a map bounding box; pass all of west/east/south/north together. Zillow autocomplete does not currently return map bounds.
`status`	No	Listing status, default for_sale. Allowed values: for_sale, for_rent, sold.
`location`	Yes	Required search location, e.g. San Francisco, CA.
`region_id`	No	Zillow region id from autocomplete; fallback geography when complete map bounds are not provided.
`region_type`	No	Zillow region type from autocomplete, used with region_id; defaults to 6 when region_id is set.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered structurally. The description adds the geography semantics (region ID as fallback when complete bounds are absent), but omits pagination behavior and the nature/format of results, so it adds only marginal context beyond annotations.

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?

Two front-loaded sentences with no repetition; the search scope and geography options come first, the sibling routing last. The phrase 'supported listing filters' is slightly vague filler, but overall it is tight.

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 rich schema coverage, an output schema, and annotations present, the description supplies enough to select and call the tool correctly. It stops short of explaining result shape or ordering, but the output schema covers returns, so only minor gaps remain.

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 all nine parameters are already documented in the schema, including the pairwise west/east/south/north constraint and defaults. The description restates the location requirement and the two geography modes without adding syntax or format detail beyond the schema, which is the baseline 3 for high-coverage schemas.

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

Purpose5/5

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

States a specific verb (Search) and resource (Zillow listings) plus the required key (location) and optional geography modes. It names the sibling zillow_property for single-property detail, so the agent can distinguish this search tool from the lookup tool without opening schemas.

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?

Explicitly routes the agent to zillow_property 'to retrieve details for one property identifier,' giving a clear alternative. It also signals that location is required, but does not state when-not to use this tool or any prerequisites beyond that.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?