Skip to main content
Glama

Search Zillow

search_zillow
Read-onlyIdempotent

Reads US home listings from a Zillow search URL and returns up to 40 listings (address, price, beds, baths, status, zestimate, url). It takes a URL, not keywords, e.g. "https://www.zillow.com/homes/Austin,-TX_rb/"; to find pages by keyword use google_search. It does not return price history, photos or agent details. A URL with no listings returns NO_DATA and is not charged. Required: url.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "search_zillow"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesZillow search URL, at most 8192 characters, e.g. "https://www.zillow.com/homes/Austin,-TX_rb/". Short forms such as "https://www.zillow.com/austin-tx/" are converted; filters go in the URL.
resultsNoMaximum listings returned, integer 1-40, default 10, e.g. 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of listings to return."New value: +"Maximum listings returned, integer 1-40, default 10, e.g. 20."
    • changedInput schema / properties / url / description
      Previous value: -"Zillow search URL, for example https://www.zillow.com/homes/Austin,-TX_rb/ (short forms like https://www.zillow.com/austin-tx/ are converted)."New value: +"Zillow search URL, at most 8192 characters, e.g. \"https://www.zillow.com/homes/Austin,-TX_rb/\". Short forms such as \"https://www.zillow.com/austin-tx/\" are converted; filters go in the URL."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the description adds useful context beyond that: it lists returned fields, states the 40-listing cap, and notes that a URL with no listings returns NO_DATA and is not charged. It does not discuss auth or rate limits, but the billing/error behavior is valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core behavior and packed with useful constraints in just a few sentences. Every sentence earns its place by clarifying input type, return shape, exclusions, and billing behavior.

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

Completeness5/5

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

Given a simple two-parameter tool with full schema coverage and no output schema, the description is complete: it explains the input format, return fields, listing cap, exclusions, and NO_DATA billing behavior. An agent has enough information to invoke it correctly.

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 fully documents both url and results. The description reinforces that url is required and gives an example, but adds little beyond the schema and does not explain the results parameter.

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 states a specific verb and resource: reads US home listings from a Zillow search URL. It distinguishes itself from keyword-search siblings by explicitly requiring a URL and naming google_search as the alternative for keyword-based discovery.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use signal (Zillow search URL) and a when-not-to-use signal (keywords), naming google_search as the correct alternative. It also clarifies exclusions such as price history, photos, and agent details.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources