Skip to main content
Glama
Sign In
zillow-mcp

zillow-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Zestimate history for a property

zillow_get_zestimate_history
Read-onlyIdempotent

Retrieve a property's historical Zestimate values and optional rent estimates by Zillow zpid or homedetails URL, returning a dated time series to analyze value trends.

Instructions

Historical Zestimate values for a property by zpid or homedetails URL. Returns a time series of {date, value, rent?} entries (rent included when Zillow has a rent Zestimate for the property). Note: zillow_get_property returns only the current Zestimate as a scalar — call this tool when you need the trend. For some listings (commonly non-Showcase) Zillow renders the trend client-side and omits it from the server-rendered page; then points is empty and an explanatory note is returned — distinct from a genuine no-history. Read-only; safe to call repeatedly.

Input Schema

NameRequiredDescriptionDefault
urlNoZillow homedetails URL (or path). Provide either zpid or url.
zpidNoZillow Property ID. Provide either zpid or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.4
    • changedInput schema / properties / zpid / anyOf
      Previous value: -[
-  {
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]
  2. 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"
  3. First observedv0.11.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description goes further by disclosing the return shape ({date, value, rent?}), when rent appears, and the empty-`points`-plus-`note` edge case that is distinct from genuine no-history. That is real behavioral context beyond what the annotations provide, even if 'read-only; safe to call repeatedly' restates the hints.

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?

Front-loaded with the core purpose, then the sibling distinction, then the edge case — a sensible ordering with no filler. The closing 'Read-only; safe to call repeatedly' is redundant with readOnlyHint/idempotentHint, a minor wasted sentence.

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 carries the return-value burden and does so: it specifies the time-series shape, the optional rent field, and the empty-result semantics. An agent has everything needed to call and interpret it.

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 both parameters (url, zpid) are fully documented in the schema, so the description adds no syntax or constraint detail beyond restating the either/or input. Baseline 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?

States a specific verb+resource (historical Zestimate values) and the exact retrieval key (zpid or homedetails URL). It explicitly distinguishes itself from the sibling zillow_get_property, which returns only the current scalar Zestimate.

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?

Gives an explicit when-to-use rule: 'call this tool when you need the trend,' and names the alternative that covers the current value. It also flags the common failure mode (client-side-rendered trend → empty points) so the agent can interpret the result rather than assume no history exists.

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