Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zillow_property

Fetch normalized Zillow public property details by property ID (zpid), including address, pricing, history, media, facts, schools, and nearby homes when available.

Instructions

Get Zillow property. Returns normalized Zillow public property details using Zillow's public persisted GraphQL property payload, including optional typed sections for address parts, listing attribution, pricing, history, media, facts, schools, and nearby homes when present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zpidYesZillow property id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions using GraphQL payload but fails to disclose behavioral traits like read-only nature, rate limits, authentication needs, or data freshness. Only describes return structure.

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 sentences, first is direct verb+resource, second adds valuable detail. No wasted words, but could be slightly more structured (e.g., bullet points for optional sections).

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?

Covers return structure with optional sections, but lacks behavioral context (e.g., whether it requires authentication, is read-only, rate limits). Without output schema, description provides adequate but not complete guidance for a straightforward lookup tool.

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% with zpid described as 'Zillow property id'. Description adds no additional meaning beyond the schema for the parameter, so baseline of 3 is appropriate.

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?

Clearly states the tool gets a Zillow property by zpid and returns normalized public property details with optional typed sections. Distinguishes from siblings like zillow_search and zillow_autocomplete which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates usage for retrieving a specific property by ID, but no explicit guidance on when to use this versus sibling tools like zillow_search or zillow_autocomplete. No when-not or alternative context provided.

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