Skip to main content
Glama
BACH-AI-Tools

Idealista7 MCP Server

list_lands

List land properties for sale or rent using filters for location, size, price, and land type such as urban or building land.

Instructions

List Lands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesExample value:
urbanNoExample value:
localeYesExample value:
maxSizeNoExample value: 0
minSizeNoExample value: 0
numPageYesExample value: 11
locationYesExample value:
maxItemsYesExample value:
maxPriceNoExample value: 0
minPriceNoExample value: 0
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
buildingLandNoExample value:
locationNameYesExample value: Madrid
nonBuildingLandNoExample value:
micrositeShortNameNoExample value:
Behavior1/5

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

With no annotations present, the description must disclose behavioral traits, but it only says 'List Lands'. No information on side effects, permissions, rate limits, or read-only status is provided.

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 short (2 words), but this is under-specification rather than conciseness. It lacks necessary detail to be useful.

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 17 parameters (8 required) and no output schema or meaningful description, the tool definition is completely inadequate. It fails to explain functionality, usage, or return values.

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 baseline is 3. However, the description itself adds no parameter information beyond the schema, which mostly has empty descriptions. Thus, it does not improve clarity.

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?

The description 'List Lands' is a tautology, merely restating the tool name. It does not clarify what constitutes a 'Land' in this context or distinguish it from sibling tools like list_buildings or list_commercial_properties.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, 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