Skip to main content
Glama
HasData

hasdata-mcp

Official

zillow_listing: GET /

hasdata_zillow_listing_getRealEstateListings

Search Zillow for real estate listings by keyword with filters on price, beds, baths, home type, and more. Returns detailed listing data for market analysis and lead generation.

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
NameRequiredDescriptionDefault
keywordYesThe keyword used to search for listings.
typeYesThe type of listing.
sortNoThe sorting option for the search results.
price[min]NoThe minimum price of the listing.
price[max]NoThe maximum price of the listing.
beds[min]NoThe minimum number of bedrooms.
beds[max]NoThe maximum number of bedrooms.
baths[min]NoThe minimum number of bathrooms.
baths[max]NoThe maximum number of bathrooms.
yearBuilt[min]NoThe minimum year the property was built.
yearBuilt[max]NoThe maximum year the property was built.
lotSize[min]NoThe minimum lot size.
lotSize[max]NoThe maximum lot size.
squareFeet[min]NoThe minimum square footage.
squareFeet[max]NoThe maximum square footage.
homeTypes[]NoAn array of home types to filter the listings.
listingTypeNoThe category of the listing.
listingPublishOptions[]NoAn array of listing publish options.
hoaNoThe Homeowners Association (HOA) fee.
propertyStatus[]NoAn array of property statuses.
tours[]NoAn array of tour options.
otherAmenities[]NoAn array of other amenities.
views[]NoAn array of views.
pets[]NoAn array of pet options.
basement[]NoAn array of basement options.
singleStoryOnlyNoIf set to true, only single-story properties will be included.
hide55plusCommunitiesNoIf set to true, 55+ communities will be excluded.
daysOnZillowNoThe number of days a listing has been on Zillow.
moveInDateNoThe desired move-in date.
mustHaveGarageNoIf set to true, only listings with a garage will be included.
parkingSpotsMinNoThe minimum number of parking spots.
keywordsNoAdditional keywords to refine the search.
pageNoThe page number of the results to retrieve.
Behavior3/5

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

No annotations are provided, so description carries full burden. It mentions pagination but does not explain how page parameter works or clarify limits. For a read tool, it is adequate but missing details on result behavior.

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 concise, front-loads purpose, and uses bullet-point-like use cases. However, the return fields list could be structured more clearly.

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

Completeness3/5

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

Given the tool's complexity (33 params), the description covers purpose and return fields but lacks details on pagination behavior, default sorting, and any limitations. It is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by listing the return fields (address, Zestimate, etc.), which are not in the schema. However, the filter listing is redundant with schema.

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?

The description clearly states it retrieves Zillow real estate listings by keyword with rich filters and pagination. It distinguishes from the sibling tool hasdata_zillow_property_getPropertyDetails by mentioning it collects URLs for that 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?

The description lists specific use cases such as market dashboards and rental analysis, and implies workflow with property endpoint. However, it does not explicitly compare with other real estate siblings like Redfin listing tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HasData/hasdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server