HasData

zillow_listing: GET /

hasdata_zillow_listing_getRealEstateListings

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.
`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. Use `ownerPosted` for listings by owner and `agentListed` for listings by agent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / listingPublishOptions__ / description

Previous value: -"An array of listing publish options."New value: +"An array of listing publish options. Use `ownerPosted` for listings by owner and `agentListed` for listings by agent."

removedInput schema / properties / listingType

Removed value: -{
-  "description": "The category of the listing.",
-  "enum": [
-    "byAgent",
-    "byOwner"
-  ],
-  "type": "string"
-}

First observedSep 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses return contents and mentions pagination, which is useful, but says nothing about rate limits, authentication, result caps, or whether pagination terminates. For a read-only search the safety profile is self-evident, but richer operational detail is missing.

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?

Front-loaded with the core purpose, followed by filters, return fields, and use cases in a logical order. It is dense but not padded; a single long sentence carries each block cleanly, though the use-case list could be trimmed slightly.

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 32-parameter, no-annotation, no-output-schema tool, the description compensates by enumerating the return fields and summarizing the filter surface. It does not fully substitute for the absence of an output schema (no response shape/nesting detail) but covers enough for correct selection and invocation.

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 description coverage is 100%, so the schema already documents every one of the 32 parameters with descriptions and enums. The description adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (Searches) and resource (Zillow for-sale/for-rent/sold listings), enumerates the filter families, and lists the returned fields. It implicitly distinguishes itself from siblings by naming the 'Zillow Property endpoint' it feeds and by scoping to Zillow rather than Redfin.

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?

Provides use-case contexts (market dashboards, rental pricing, lead lists, inventory tracking, collecting URLs for the Property endpoint), which implies when to reach for it. However, it never states when NOT to use it or explicitly contrasts with the sibling hasdata_zillow_property_getPropertyDetails or hasdata_redfin_listing_getRealEstateListings.

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

All HasData tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

zillow_listing: GET /

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources