HasData MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

zillow_listing: GET /

hasdata_zillow_listing_getRealEstateListings

Search Zillow listings by keyword with filters for price, beds, baths, and home type. Get address, price, beds/baths, sqft, and agent details for market analysis.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description
`hoa`	No	The Homeowners Association (HOA) fee.
`page`	No	The page number of the results to retrieve.
`sort`	No	The sorting option for the search results.
`type`	Yes	The type of listing.
`pets__`	No	An array of pet options.
`keyword`	Yes	The keyword used to search for listings.
`tours__`	No	An array of tour options.
`views__`	No	An array of views.
`keywords`	No	Additional keywords to refine the search.
`beds_max_`	No	The maximum number of bedrooms.
`beds_min_`	No	The minimum number of bedrooms.
`basement__`	No	An array of basement options.
`baths_max_`	No	The maximum number of bathrooms.
`baths_min_`	No	The minimum number of bathrooms.
`moveInDate`	No	The desired move-in date in `YYYY-MM-DD` format.
`price_max_`	No	The maximum price of the listing.
`price_min_`	No	The minimum price of the listing.
`homeTypes__`	No	An array of home types to filter the listings.
`listingType`	No	The category of the listing.
`daysOnZillow`	No	The number of days a listing has been on Zillow.
`lotSize_max_`	No	The maximum lot size.
`lotSize_min_`	No	The minimum lot size.
`mustHaveGarage`	No	If set to true, only listings with a garage will be included.
`yearBuilt_max_`	No	The maximum year the property was built.
`yearBuilt_min_`	No	The minimum year the property was built.
`parkingSpotsMin`	No	The minimum number of parking spots.
`singleStoryOnly`	No	If set to true, only single-story properties will be included.
`squareFeet_max_`	No	The maximum square footage.
`squareFeet_min_`	No	The minimum square footage.
`otherAmenities__`	No	An array of other amenities.
`propertyStatus__`	No	An array of property statuses.
`hide55plusCommunities`	No	If set to true, 55+ communities will be excluded.
`listingPublishOptions__`	No	An array of listing publish options.

Schema Changelog

Changes observed during successful MCP inspections.

Changed41 schema fields changedv1.0.2Sep 11, 2026

removedInput schema / properties / basement[]

Removed value: -{
-  "description": "An array of basement options.",
-  "items": {
-    "enum": [
-      "finished",
-      "unfinished"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / basement__

Added value: +{
+  "description": "An array of basement options.",
+  "items": {
+    "enum": [
+      "finished",
+      "unfinished"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / baths[max]

Removed value: -{
-  "description": "The maximum number of bathrooms.",
-  "type": "number"
-}

removedInput schema / properties / baths[min]

Removed value: -{
-  "description": "The minimum number of bathrooms.",
-  "type": "number"
-}

addedInput schema / properties / baths_max_

Added value: +{
+  "description": "The maximum number of bathrooms.",
+  "type": "number"
+}

addedInput schema / properties / baths_min_

Added value: +{
+  "description": "The minimum number of bathrooms.",
+  "type": "number"
+}

removedInput schema / properties / beds[max]

Removed value: -{
-  "description": "The maximum number of bedrooms.",
-  "type": "number"
-}

removedInput schema / properties / beds[min]

Removed value: -{
-  "description": "The minimum number of bedrooms.",
-  "type": "number"
-}

addedInput schema / properties / beds_max_

Added value: +{
+  "description": "The maximum number of bedrooms.",
+  "type": "number"
+}

addedInput schema / properties / beds_min_

Added value: +{
+  "description": "The minimum number of bedrooms.",
+  "type": "number"
+}

removedInput schema / properties / homeTypes[]

Removed value: -{
-  "description": "An array of home types to filter the listings.",
-  "items": {
-    "enum": [
-      "house",
-      "townhome",
-      "multiFamily",
-      "condo",
-      "lot",
-      "apartment",
-      "manufactured"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / homeTypes__

Added value: +{
+  "description": "An array of home types to filter the listings.",
+  "items": {
+    "enum": [
+      "house",
+      "townhome",
+      "multiFamily",
+      "condo",
+      "lot",
+      "apartment",
+      "manufactured"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / listingPublishOptions[]

Removed value: -{
-  "description": "An array of listing publish options.",
-  "items": {
-    "enum": [
-      "ownerPosted",
-      "agentListed",
-      "newConstruction",
-      "foreclosures",
-      "auctions",
-      "foreclosed",
-      "preForeclosures"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / listingPublishOptions__

Added value: +{
+  "description": "An array of listing publish options.",
+  "items": {
+    "enum": [
+      "ownerPosted",
+      "agentListed",
+      "newConstruction",
+      "foreclosures",
+      "auctions",
+      "foreclosed",
+      "preForeclosures"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / lotSize[max]

Removed value: -{
-  "description": "The maximum lot size.",
-  "type": "number"
-}

removedInput schema / properties / lotSize[min]

Removed value: -{
-  "description": "The minimum lot size.",
-  "type": "number"
-}

addedInput schema / properties / lotSize_max_

Added value: +{
+  "description": "The maximum lot size.",
+  "type": "number"
+}

addedInput schema / properties / lotSize_min_

Added value: +{
+  "description": "The minimum lot size.",
+  "type": "number"
+}

changedInput schema / properties / moveInDate / description

Previous value: -"The desired move-in date."New value: +"The desired move-in date in `YYYY-MM-DD` format."

removedInput schema / properties / otherAmenities[]

Removed value: -{
-  "description": "An array of other amenities.",
-  "items": {
-    "enum": [
-      "ac",
-      "pool",
-      "waterfront",
-      "onsiteParking",
-      "inUnitLaundry",
-      "acceptZillowApplications",
-      "incomeRestricted",
-      "apartmentCommunity"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / otherAmenities__

Added value: +{
+  "description": "An array of other amenities.",
+  "items": {
+    "enum": [
+      "ac",
+      "pool",
+      "waterfront",
+      "onsiteParking",
+      "inUnitLaundry",
+      "acceptZillowApplications",
+      "incomeRestricted",
+      "apartmentCommunity"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / pets[]

Removed value: -{
-  "description": "An array of pet options.",
-  "items": {
-    "enum": [
-      "allowsLargeDogs",
-      "allowsSmallDogs",
-      "allowsCats"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / pets__

Added value: +{
+  "description": "An array of pet options.",
+  "items": {
+    "enum": [
+      "allowsLargeDogs",
+      "allowsSmallDogs",
+      "allowsCats"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / price[max]

Removed value: -{
-  "description": "The maximum price of the listing.",
-  "type": "number"
-}

removedInput schema / properties / price[min]

Removed value: -{
-  "description": "The minimum price of the listing.",
-  "type": "number"
-}

addedInput schema / properties / price_max_

Added value: +{
+  "description": "The maximum price of the listing.",
+  "type": "number"
+}

addedInput schema / properties / price_min_

Added value: +{
+  "description": "The minimum price of the listing.",
+  "type": "number"
+}

removedInput schema / properties / propertyStatus[]

Removed value: -{
-  "description": "An array of property statuses.",
-  "items": {
-    "enum": [
-      "comingSoon",
-      "acceptingBackupOffers",
-      "pendingAndUnderContract"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / propertyStatus__

Added value: +{
+  "description": "An array of property statuses.",
+  "items": {
+    "enum": [
+      "comingSoon",
+      "acceptingBackupOffers",
+      "pendingAndUnderContract"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / squareFeet[max]

Removed value: -{
-  "description": "The maximum square footage.",
-  "type": "number"
-}

removedInput schema / properties / squareFeet[min]

Removed value: -{
-  "description": "The minimum square footage.",
-  "type": "number"
-}

addedInput schema / properties / squareFeet_max_

Added value: +{
+  "description": "The maximum square footage.",
+  "type": "number"
+}

addedInput schema / properties / squareFeet_min_

Added value: +{
+  "description": "The minimum square footage.",
+  "type": "number"
+}

removedInput schema / properties / tours[]

Removed value: -{
-  "description": "An array of tour options.",
-  "items": {
-    "enum": [
-      "open",
-      "3d"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / tours__

Added value: +{
+  "description": "An array of tour options.",
+  "items": {
+    "enum": [
+      "open",
+      "3d"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / views[]

Removed value: -{
-  "description": "An array of views.",
-  "items": {
-    "enum": [
-      "city",
-      "mountain",
-      "park",
-      "water"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / views__

Added value: +{
+  "description": "An array of views.",
+  "items": {
+    "enum": [
+      "city",
+      "mountain",
+      "park",
+      "water"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / yearBuilt[max]

Removed value: -{
-  "description": "The maximum year the property was built.",
-  "type": "number"
-}

removedInput schema / properties / yearBuilt[min]

Removed value: -{
-  "description": "The minimum year the property was built.",
-  "type": "number"
-}

addedInput schema / properties / yearBuilt_max_

Added value: +{
+  "description": "The maximum year the property was built.",
+  "type": "number"
+}

addedInput schema / properties / yearBuilt_min_

Added value: +{
+  "description": "The minimum year the property was built.",
+  "type": "number"
+}

Addedv1.0.1May 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return behavior by listing output fields and uses 'Searches'/'Returns' implying read-only, but it does not mention auth requirements, rate limits, or explicitly state that no data is modified.

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?

The description is compact and well-structured: a terse title line, a summary of functionality, and a list of use cases. It avoids unnecessary detail, though the opening 'Get Zillow Real Estate Listings' is slightly redundant with the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 33 parameters and no output schema, the description provides sufficient context: what it searches, what it returns, and when to use it. It does not explain pagination defaults or required-field relationships, but the schema already marks 'keyword' and 'type' as required.

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% with descriptions for all 33 parameters. The description adds only a high-level grouping of filter types ('price, beds, baths, home type, year built...') rather than clarifying individual parameters, so it stays at the baseline.

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?

Description clearly states the tool 'Searches Zillow for-sale, for-rent, and sold listings by keyword' and specifies the output fields. It distinguishes from the sibling property-details tool by emphasizing listing search and 'collecting URLs for the Zillow Property endpoint.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: 'real-estate market dashboards, rental pricing analysis, agent lead lists, inventory tracking, and collecting URLs for the Zillow Property endpoint.' This gives clear context for when to use the tool, though it doesn't explicitly say 'use this instead of getPropertyDetails.'

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

Deploy Server

zillow_listing: GET /

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools