Retrieve Zillow property details by ZPID, including address, pricing, listing attribution, history, media, facts, schools, and nearby homes when available.
Get Zillow property. Returns Zillow property details, including optional typed sections for address parts, listing attribution, pricing, history, media, facts, schools, and nearby homes when present.
| Name | Required | Description | Default |
|---|---|---|---|
| zpid | Yes | Zillow property id |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden; it does disclose the returned content shape and signals optionality with 'when present', which is genuinely useful. However, it says nothing about the read-only nature, error behavior for an invalid zpid, or whether all sections are always fetched.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with the core action and then the return payload. No filler, though the section list is somewhat long.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description usefully enumerates the return sections, but it omits how to obtain the zpid and any retrieval context. Adequate for a single-param getter, but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the sole parameter zpid is already documented as 'Zillow property id'. The description adds no format, sourcing, or syntax detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get Zillow property') and enumerates the returned sections (address, pricing, history, media, facts, schools, nearby homes), which lets an agent distinguish it from zillow_search or zillow_autocomplete. It does not explicitly name those siblings, 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance: it never says the zpid must come from zillow_search/zillow_autocomplete, nor when to prefer this over the other Zillow tools. The agent must infer the retrieval workflow entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.