zillow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_homesA | Search Zillow for homes in an area. Give it a plain location -- a city and state ('Austin, TX'), a ZIP code ('78704'), or a neighborhood -- plus optional filters. Returns each listing's address, price, beds, baths, sqft, Zillow property ID (zpid), listing URL, and days on Zillow. status: 'rent' (default), 'sale', or 'sold' (recently sold). sort: one of relevant, newest, price_asc, price_desc, beds, baths, sqft, lot_size (default 'relevant'). min_price/max_price, min_beds/max_beds, min_baths/max_baths: numeric filters, all optional and independent. page: 1-indexed results page (default 1). This is an unofficial, reverse-engineered method -- it fetches Zillow's own search-results pages, not an API. It can get blocked by Zillow's bot detection, and it will say so clearly when that happens rather than return something that looks like results but isn't. Only searches an area; a full street address as the location will fail with an explanation rather than returning that one property's page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined and self-contained.
The one tool name follows a conventional verb_noun pattern (search_homes) and there are no conflicting conventions to create inconsistency.
A single tool feels thin for a server named after a major real estate platform, but the tool is richly parameterized and may be intentionally scoped to search only. It falls into the borderline area for count.
Home search is covered thoroughly with many filters, but the server lacks property-detail lookup by Zillow ID, address-specific searches, or history/listing-related tools. Agents can find homes but cannot go deeper without leaving the MCP.