Skip to main content
Glama
zillow-mcp

zillow-mcp

by chrischall

Get Zillow property photo gallery

zillow_get_property_photos
Read-onlyIdempotent

Retrieve every photo from a Zillow property listing using its zpid or URL, returning hero and high-res image URLs for galleries.

Instructions

The full photo gallery for a Zillow property — every image embedded in the homedetails page. Each entry returns the canonical hero URL plus the widest jpeg + webp variants and caption when present. Provide exactly one of zpid or url. Set include_sources: true to also include the full multi-width source lists (warning: a 50+ photo property can exceed the per-call token budget). Returns { zpid, count, photos, street_view_url?, high_res_url? }. Read-only; safe to call repeatedly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zillow_get_property_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA Zillow homedetails URL (or path beginning with /homedetails/)
zpidNoZillow Property ID (numeric)
include_sourcesNoInclude the full multi-width jpeg + webp source lists per photo (default false; on for properties with <~15 photos).

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the 'read-only; safe to call repeatedly' line is largely redundant. However, the description adds genuinely new behavioral context: the token-budget warning for large galleries and the exact return shape. That is real value beyond the structured fields.

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?

Every sentence carries a distinct payload — scope, return contents, parameter constraint, opt-in flag with warning, and return shape — and the most important scoping information is front-loaded. No filler.

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 naming the returned keys (zpid, count, photos, street_view_url, high_res_url) and by flagging the one real failure mode (token overflow on 50+ photo properties). Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not encode: the mutual exclusivity of zpid and url ('provide exactly one of') and the practical guidance that include_sources is on by default for properties under ~15 photos.

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 and resource ('full photo gallery for a Zillow property') and scopes it to images embedded in the homedetails page, which clearly separates it from the sibling zillow_get_property and history tools.

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?

It gives the selection rule between the two input modes ('provide exactly one of zpid or url') and a condition for include_sources, but never says when to prefer this tool over zillow_get_property or zillow_bulk_get. Usage is implied by the tool name rather than stated.

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