Skip to main content
Glama
BACH-AI-Tools

Idealista7 MCP Server

list_commercial_properties

Search and list commercial property listings from Idealista with filters for location, price, size, property type, and more.

Instructions

List Commercial Properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesExample value:
localeYesExample value:
retailNoExample value:
streetNoExample value:
maxSizeNoExample value:
minSizeNoExample value:
numPageYesExample value: 11
cateringNoExample value:
locationYesExample value:
maxItemsYesExample value:
maxPriceNoExample value:
minPriceNoExample value:
pharmacyNoExample value:
premisesNoExample value:
foodTradeNoExample value:
mezzanineNoExample value:
newsstandNoExample 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
laboratoryNoExample value:
locationIdYesExample value: 0-EU-ES-28-07-001-079
ontopfloorNoExample value:
storehouseNoExample value:
tobaccoShopNoExample value:
undergroundNoExample value:
locationNameYesExample value: Madrid
accommodationNoExample value:
otherLocationsNoExample value:
shoppingcenterNoExample value:
barsAndNightclubNoExample value:
sportsFacilitiesNoExample value:
educationalCenterNoExample value:
saleWarehouseOnlyNoExample value:
aestheticAndBeautyNoExample value:
industrialBuildingNoExample value:
professionalServicesNoExample value:
otherCommercialActivitiesNoExample value:
saleWarehouseThirdPartiesRentedNoExample value:
saleWarehouseWithBusinessTransferNoExample value:
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It merely says 'List' but does not disclose pagination, performance, rate limits, or any side effects. The tool likely returns a list of properties but the description is silent on what 'list' entails.

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

Conciseness1/5

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

The description is only 4 words long and fails to convey any useful information. It is severely underspecified, making it virtually useless for an AI agent.

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?

Given the tool has 39 parameters, no output schema, and a trivial description, it is completely inadequate. An agent needs far more context about parameter usage, response format, and filtering behavior to invoke this tool correctly.

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?

The schema has 39 parameters with 100% description coverage, but the descriptions are mostly empty 'Example value: ' placeholders, providing no actual semantic meaning. The main description adds no information about the parameters, so the agent cannot infer which parameters are filters or how they relate to the commercial properties.

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

Purpose2/5

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

The description 'List Commercial Properties' is essentially a tautology, restating the tool name without adding any specific or distinguishing information. It does not clarify what kind of properties or what operations are involved beyond the name.

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?

There is no guidance on when to use this tool versus its siblings (e.g., list_home_properties, list_offices). The description does not mention filtering criteria, typical use cases, or any context that would help an agent decide to invoke this tool.

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