Zillow Listing Details MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call requires one. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_zillow_listingsA | Read Zillow home details by listing URL, ZPID, or street address, or list homes by 5 digit ZIP code. Returns one flat row per home with price, Zestimate, beds, baths, area, status, and the listing agent shown on MLS listings. Blocked and missing homes are free rows. Costs 0.006 USD per home page read, 0.002 USD per ZIP code search row, plus 0.007 USD per run start. |
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 one tool there is no risk of misselection between tools. However, that single tool internally conflates two distinct modes (ZIP-code search vs. single-home detail lookup), which the description explains but does not separate.
The lone name follows a clean verb_noun snake_case pattern (read_zillow_listings) and is descriptive of the domain. There is no second name to confirm a consistent convention, so it can't be a full 5.
A single tool is thin even for a narrow read-only domain; the search-by-ZIP and fetch-detail behaviors would more naturally be two tools. Agents also cannot opt into just a cheap ZIP search without invoking the same surface.
Lookup by URL, ZPID, and address plus ZIP search covers the core read workflows, and read-only is appropriate since Zillow is a data source. Gaps remain around filtering (price/beds ranges), pagination, and any bulk or comparison operations.