Crawlora MCP

zillow_property

Read-only

Fetch public Zillow property detail data, including pricing, listing status, history, media, and available property facts. Use zillow_search or zillow_autocomplete to discover the property and obtain its 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": {
      "zpid": "<zpid>"
    },
    "name": "zillow_property"
  }
}

Input Schema

Name	Required	Description	Default
`zpid`	Yes	Required Zillow property id (zpid), e.g. 12345678.

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, and an output schema exists, so the safety and return-shape burden is largely covered. The description adds modest context by calling the data 'public' and referring to 'available property facts' (hinting some facts may be absent), but discloses nothing about rate limits, auth, or missing-data behavior.

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?

Two tightly written sentences with zero filler. The data scope is front-loaded and the how-to-get-the-id guidance follows immediately.

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

Completeness5/5

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

For a single-parameter detail fetcher with an output schema and read-only annotations, the description is sufficient: it names the data returned and explains how to supply the id. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single zpid parameter is fully documented with an example, so the baseline is 3. The description only confirms that an identifier is needed and where to get it, adding workflow context but no syntax beyond the schema.

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 and resource ('Fetch public Zillow property detail data') and enumerates the returned categories (pricing, listing status, history, media, facts). It positions itself relative to zillow_search/zillow_autocomplete but doesn't draw a hard boundary, so it's clear without being maximally discriminating.

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?

Tells the agent how to obtain the required identifier by pointing to zillow_search or zillow_autocomplete, which effectively signals when this tool applies (once you have a zpid). No explicit when-not-to-use case is given, so it's strong context rather than full routing.

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?