Skip to main content
Glama
chrischall

zillow-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare multiple Zillow properties side-by-side

zillow_compare_properties
Read-onlyIdempotent

Compare 2-25 Zillow properties side-by-side to evaluate listings in one view. Get full property records plus a pivoted summary table for quick field-by-field analysis.

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`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.11.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond what readOnlyHint/openWorldHint/idempotentHint already convey, the description discloses per-row error isolation, a concurrency cap of 6 in-flight requests, retry-once-on-timeout behavior, and default omissions of description and summary. This is rich behavioral context that helps the agent predict partial failures and response weight.

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?

The description is front-loaded with purpose and the key alternative, then moves methodically through inputs, output, and failure behavior. It is dense but mostly earns its length. Some internal issue references ('Issue #79', 'issue #78') are changelog-style noise that an agent does not need for invocation.

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?

With no output schema, the description compensates by clearly describing the return shape: full per-property records per row, extracted_features populated, optional pivoted summary, and behavior when a single zpid fails. Together with the schema and annotations, an agent has enough context to call this tool correctly and interpret results.

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 the baseline is 3. The description adds value beyond the schema by explaining when to use zpids vs urls, how include_summary affects response weight, and why include_description defaults off. It doesn't fully re-document each parameter, but it adds meaningful usage context.

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 uses a specific verb and resource: 'Side-by-side analysis of 2-25 Zillow properties.' It clearly scopes the tool to comparing properties rather than fetching them, and explicitly names the sibling it is not (zillow_bulk_get), so an agent can distinguish it from related tools.

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 states exactly when to use this tool versus zillow_bulk_get: use compare for genuine side-by-side analysis, use bulk_get when you just want N property records. It also explains optional flags (include_summary, include_description) and their defaults, giving clear invocation guidance.

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