Related Servers

Most tools target distinct resources like agents, builders, properties, or market data, but there is notable overlap in search tools (e.g., search_address_search_for_a_property_by_address, search_coordinates_search_for_properties_by_coordinates, search_search_for_properties_by_neighborhood_city_or_zip) that could confuse agents on which to use for location-based queries. Additionally, property_deprecated and propertyv2_property_details_by_zpid serve similar purposes, though the deprecated tag helps clarify.

Naming is highly inconsistent with mixed patterns: some use snake_case (agent_details_by_username), some use camelCase-like concatenation (builderscommunity_cards_builders_community_cards), and others have verbose, redundant names (search_address_search_for_a_property_by_address). There is no uniform verb_noun structure, making it hard to predict tool names.

With 37 tools, the count is excessive for a real estate data server, leading to bloat and potential confusion. Many tools could be consolidated (e.g., multiple similar property search variants), and the high number suggests poor scoping, making it cumbersome for agents to navigate efficiently.

The tool set covers a broad range of real estate domains including agents, builders, lenders, properties, market data, and searches, with good CRUD-like coverage for details, reviews, and listings. Minor gaps exist, such as lack of tools for updating or deleting data (likely read-only by design), but overall it provides comprehensive access to Zillow's data surface.