Skip to main content
Glama
BACH-AI-Tools

Idealista7 MCP Server

list_garages

Search and list garage listings for rent or sale in Spain, Portugal, and Italy with filters like location, price, size, and sorting.

Instructions

List garages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesOrder by one of the followings: relevance|lowestprice|highestprice|mostrecent|leastrecent|highestpricereduction|lowestpricem2|highestpricem2|biggest|smallest|highestfloors|lowestfloors Default is relevance.
localeYesExample value:
maxSizeNoExample value: 0
minSizeNoExample value: 0
numPageYesExample value: 11
locationYesExample value:
maxItemsYesExample value:
maxPriceNoExample value: 0
minPriceNoExample value: 0
securityNoExample value:
operationYesExample value:
sinceDateNoPublication Date Parameter. One of the following values. Indifferent: leave blank (by default) | Last 24h: T (Rent operation only) | Last 48h: Y (Buy operation only) | Last week: W | Last month: M
locationIdYesExample value: 0-EU-ES-28-07-001-079
locationNameYesExample value: Madrid
automaticDoorNoExample value:
motorcycleParkingNoExample value:
micrositeShortNameNoGet ads from a specific real estate. For example if the URL from the real estate is: https://www.idealista.com/pro/cajal-gestion-inmobiliaria/ The parameter micrositeShortName should be cajal-gestion-inmobiliaria
Behavior1/5

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

No annotations are present, and the description does not disclose behavioral traits such as read-only nature, pagination, data freshness, rate limits, or side effects. The agent has no insight into how the tool operates.

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

Conciseness2/5

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

The description is extremely concise (two words) but at the cost of informativeness. It is under-specified, lacking any structure or front-loaded key information. Effective conciseness should balance brevity with clarity, which is missing here.

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

Completeness1/5

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

With 17 parameters, 8 required, no output schema, and no annotations, the description is critically incomplete. It fails to explain what properties are returned, how sorting works, or any prerequisite conditions. The agent cannot effectively use this tool without additional documentation.

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?

Schema coverage is 100%, but many parameter descriptions are uninformative (e.g., 'Example value: ' with empty values). The description adds no extra meaning beyond the schema, failing to compensate for poor parameter documentation. Agent would struggle to correctly fill parameters like 'locale' or 'location'.

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

Purpose1/5

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

Description 'List garages' is a tautology that restates the name without adding any specificity. It fails to distinguish this tool from sibling tools like list_buildings or list_home_properties, as it does not clarify what a 'garage' is in this context (likely parking spaces).

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

Usage Guidelines1/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. There is no discussion of prerequisites, typical scenarios, or exclusion criteria, leaving the agent to guess based on the name alone.

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