Skip to main content
Glama
BACH-AI-Tools

Zoopla MCP Server

propertiesv2list

Search UK properties for sale or rent using location, price, beds, and other filters to find listings matching specific criteria.

Instructions

List properties for sale or rent with options and filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationValueYesThe value of geoLabel field returned in .../v2/auto-complete endpoint with listings as search_type. Or the value of name field returned in .../house-prices/v2/get-area (If you are searching by postal code). You must use EXACTLY the value returned by the endpoint. *'listing_id' OR 'area' parameter must be provided to get this endpoint working.
locationIdentifierYesThe value of geoIdentifier field returned in .../v2/auto-complete endpoint with listings as search_type. Or the value of id field returned in ..../house-prices/v2/get-area endpoint (If you are searching by postal code). You must use EXACTLY the value returned by the endpoint.
categoryNoOne of the following residential|commercial
furnishedStateNoOne of the following : Any|furnished|part_furnished|unfurnished
includeRentedNoExample value:
includeRetirementHomesNoExample value:
includeSharedAccommodationNoExample value:
includeSharedOwnershipNoExample value:
includeSoldNoExample value:
isAuctionNoExample value:
petsAllowedNoExample value:
billsIncludedNoExample value:
keywordsNoAny word or term, ex : garden,wooden floors
sectionNoOne of the following : for-sale|to-rent
bedsMaxNoMax number of bed rooms (1 - 10)0
bedsMinNoMin number of bed rooms (1 - 10)0
priceMaxNoMaximum sale or rent price0
priceMinNoMinimum sale or rent price0
sortOrderNoOne of the following : newest_listings|highest_price|lowest_price|most_reduced
pageNoThe page index for paging purpose1
radiusNoThe radius (miles) to look for properties (0.25 - 40)0
priceFrequencyNoOne of the following per_month|per_year
newHomesNoOne of the following : only|exclude
addedNoRecently added. One of the following : 24_hours|3_days|7_days|14_days|30_days
propertySubTypeNoFilter properties by category. Ignore OR one of the followings (Separated by comma for multiple options) : park_home,bungalow,farms_land,terraced,flats,semi_detached,detached
chainFreeNoExample value:
reducedPriceOnlyNoExample value:
featureNoOne of the followings : has_balcony_terrace|has_parking_garage|has_garden . Separated by comma for multiple options. Ex : has_balcony_terrace,has_parking_garage,...
tenureNoOne of the followings : share_of_freehold|freehold|leasehold. Ex : freehold,leasehold,...
smartTagsNoOne of the followings : condition.needs_modernisation|architecture.period_property|type.cottage|style.modern|attributes.utility_room|attributes.basement|attributes.conservatory|attributes.home_office|attributes.bath|attributes.en_suite|attributes.patio|attributes.kitchen_island. Ex : condition.needs_modernisation,architecture.period_property,...
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'options and filters' but doesn't disclose critical behaviors like pagination (implied by 'page' parameter), rate limits, authentication needs, or what the output looks like (no output schema). This is inadequate for a tool with 30 parameters.

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 a single, efficient sentence that front-loads the core purpose ('List properties for sale or rent') and adds a brief qualifier ('with options and filters'). There is no wasted verbiage, making it highly concise and well-structured.

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

Completeness2/5

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

Given the complexity (30 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain the tool's behavior, output format, or usage context relative to siblings. For a search/list tool with many filters, more guidance is needed to help an agent use it effectively.

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 fully documents all 30 parameters. The description adds no additional parameter semantics beyond mentioning 'options and filters', which is already implied by the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('properties for sale or rent'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'propertiesv2detail' or 'propertieslist_deprecated', which likely serve different purposes (detail view vs. deprecated version).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'propertiesv2detail' for detailed property information or 'v2auto_complete' for location lookups, leaving the agent without context for tool selection.

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/BACH-AI-Tools/bachai-zoopla'

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