{
"name": "searchapi_zillow",
"description": "Zillow Search results from SearchApi, as structured JSON.",
"input_schema": {
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Location query, e.g. \"New York, NY\"."
},
"search_type": {
"type": "string",
"description": "Listing type to search.",
"enum": [
"for_sale",
"for_rent",
"sold"
]
},
"price_min": {
"type": "integer",
"description": "Minimum price filter."
},
"price_max": {
"type": "integer",
"description": "Maximum price filter."
},
"beds_min": {
"type": "integer",
"description": "Minimum bedrooms filter."
},
"baths_min": {
"type": "integer",
"description": "Minimum bathrooms filter."
},
"sort_by": {
"type": "string",
"description": "Order of the listings, e.g. relevance, newest, price_high, price_low."
},
"page": {
"type": "integer",
"description": "Page number of the results.",
"default": 1
}
},
"required": [
"q"
],
"examples": [
{
"q": "coffee"
}
]
}
}
Paste the definition into your own agent's tools array. The schema is generated from this engine's catalog entry, and the reader's configured values ride in the schema's examples. The name is ours rather than the MCP server's — it is what your agent will call — and every engine's is prefixed searchapi_.