Skip to main content
Glama
BACH-AI-Tools

Idealista7 MCP Server

list_new_homes

List new home properties for sale or rent using filters such as price, bedrooms, and location. Sort results by relevance, price, or date.

Instructions

List new home properties with the requested parameters. Buy/Rent \u003e New home. Filters are optional parameters, please make sure the request follows the rules in each parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flatsNoExample value:
orderYesOrder by one of the followings: relevance|lowestprice|highestprice|mostrecent|leastrecent|highestpricereduction|lowestpricem2|highestpricem2|biggest|smallest|highestfloors|lowestfloors Default is relevance.
localeYesExample value:
numPageYesExample value: 1
finishedNoExample value:
locationYesExample value:
maxItemsYesExample value: 40
maxPriceNoExample value:
minPriceNoExample value:
bankOfferNoExample value:
bedrooms0NoExample value:
bedrooms1NoExample value:
bedrooms2NoExample value:
bedrooms3NoExample value:
bedrooms4NoExample value:
operationYesSearch sales or rentals. Pick between: sale|rent
rentToOwnNoExample value:
locationIdYesExample value: 0-EU-ES-28-07-001-079
locationNameYesExample value: Madrid
housesOrChaletsNoExample value:
stateSubsidizedNoExample value:
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says to follow parameter rules, but omits details like pagination, result format, or error handling, leaving the agent with insufficient transparency.

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 with two sentences front-loading the purpose. While efficient, it could be better structured with distinct sections for usage notes.

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 high parameter count, required fields, and many sibling tools, the description is incomplete. It lacks details on what constitutes a 'new home,' how filtering works, and what the response provides, leaving gaps for the agent.

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

Parameters2/5

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

Although schema coverage is 100%, most parameter descriptions are empty placeholders. The tool description adds no meaningful semantic help beyond the schema, failing to clarify usage or format for the 21 parameters.

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 tool lists new home properties, identifying the resource and action. However, it does not differentiate from sibling tools like list_home_properties, which might also list new homes.

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 mentions filters are optional but provides no guidance on when to use this tool versus alternatives, nor does it specify any prerequisites or exclusions.

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/idealista7'

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