Zillow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
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 |
|---|---|
| hasdata_zillow_listing_getRealEstateListingsA | Get Zillow Real Estate Listings Searches Zillow for-sale, for-rent, and sold listings by keyword with rich filters (price, beds, baths, home type, year built, lot/square footage, HOA, listing status, amenities, views, pet policy, days on Zillow) and pagination. Returns each listing with address, Zillow URL/zpid, price, Zestimate, beds/baths, sqft, home type, status, days on Zillow, coordinates, thumbnail, and listing agent. Use for real-estate market dashboards, rental pricing analysis, agent lead lists, inventory tracking, and collecting URLs for the Zillow Property endpoint. |
| hasdata_zillow_property_getPropertyDetailsA | Get Zillow Property Details Fetches the full Zillow property page by URL/zpid, with optional agent email extraction. Returns address, list price, Zestimate and Rent Zestimate, price and tax history, beds/baths, living area, lot size, year built, home type, HOA, days on Zillow, listing description, features/amenities, photos, school assignments, walk/transit scores, and listing agent/broker (plus email when enabled). Use for valuation models, CMA generation, investor underwriting, rental yield analysis, and enriching buyer/seller agent assistants with authoritative property data. |
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 2 tools
The two tools have distinct jobs: one searches for listings and returns listing-level records, while the other fetches the full property page for a URL or zpid. The search tool also explicitly identifies itself as the entry point for the property endpoint, so an agent can assign each task easily.
Both names follow the same hasdata_zillow_entity_getThing pattern, so the set is predictable and readable. The minor inconsistency is that the verb portion is verbose and slightly redundant in different ways: getRealEstateListings versus getPropertyDetails, which makes them consistent but not perfectly parallel.
Two tools is at the borderline: the pair works well together as a search-then-details workflow, but the server is thin for a general-purpose Zillow data source. A property lookup by address or an agent lookup tool would make the count feel more complete.
The listing search plus property details covers the core real-estate data workflow: find properties, collect URLs, then fetch the full property record. The main gap is that agents cannot directly look up a property by address without first performing a keyword search, but that is a workaround through the existing search tool.