Skip to main content
Glama
chrischall

zillow-mcp

by chrischall

Compare multiple Zillow properties side-by-side

zillow_compare_properties
Read-onlyIdempotent

Compare 2 to 25 Zillow properties side-by-side. Get full records per property and an optional pivoted summary table for easy comparison.

Instructions

Side-by-side analysis of 2-25 Zillow properties. If you just want N property records, use zillow_bulk_get instead — compare is for genuine side-by-side (its pivoted summary table is the value-add); bulk_get is the fetch-many endpoint and accepts up to 200 ids. (Issue #79 raised this cap from 8 to 25 — a 19-listing analysis now fits in one call instead of three.) Provide an array of zpids (or homedetails URLs). Returns the full per-property record per row (with extracted_features populated). Pass include_summary: true for an extra pivoted summary table (one row per field) — defaults off because results[].property.* already carries everything. The raw description is omitted from each row by default — pass include_description: true to keep it. Errors for individual properties are captured per-row — one bad zpid won't fail the whole call. Calls fan out concurrently (capped at 6 in flight, per issue #78, with retry-once-on-timeout per sub-request to absorb transient SW evictions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoArray of 2-25 Zillow homedetails URLs/paths to compare. Provide either zpids or urls.
zpidsNoArray of 2-25 zpids to compare. Provide either zpids or urls. For larger batches, use `zillow_bulk_get`.
include_summaryNoInclude the pivoted `summary` table (one row per compared field, one column per listing). Defaults to `false` because `results[].property.*` already carries everything — the summary roughly doubles response weight and is mainly useful for human-readable rendering.
include_descriptionNoInclude the raw `description` on each row. Defaults to `false`.
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint, idempotentHint), the description adds substantial behavioral context: concurrency capped at 6 with retry-once-on-timeout, per-row error handling (one bad zpid doesn't fail the call), default behavior for optional fields, and a note about the cap increase from 8 to 25. No contradictions.

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?

The description is dense but efficient, front-loading the key distinction from a sibling tool. Every sentence earns its place, covering input constraints, optional parameters, behavior, and error handling without redundancy. It is neither too long nor too short.

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?

Given the complexity of the tool (4 parameters, arrays, concurrency, error handling, optional summary), the description covers all relevant aspects: input format, size limits, default behaviors, concurrent fan-out, and error resilience. No output schema is provided, but the description states return format (per-property record with extracted_features).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the mutual exclusivity of 'urls' and 'zpids', the rationale behind default values for 'include_summary' (redundancy with results) and 'include_description' (omitted by default), and the size constraint (2-25).

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?

The description clearly states the tool performs side-by-side analysis of 2-25 Zillow properties, with a specific verb ('compare') and resource ('Zillow properties'). It distinguishes itself from the sibling tool `zillow_bulk_get` by explicitly stating when to use which.

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

Usage Guidelines5/5

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

The description provides explicit guidance: use this for genuine side-by-side analysis (value-add is the pivoted summary table) and `zillow_bulk_get` for fetching up to 200 records. It also clarifies input format (zpids or URLs) and constraints (2-25 items).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/zillow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server