Get guidance on Idealista screens and the sign-in link to list and update property listings; call this first.
How to work in Idealista (list and update your listings): its screens and the sign-in link. Call this first.
| Name | Required | Description | Default |
|---|---|---|---|
| task | No | What you want done in Idealista, in your words. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It indicates that the tool provides screens and a sign-in link, but it does not explicitly state that it only returns guidance, performs no site actions, or whether authentication is required before other tools can be used.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: it states the tool's role, lists what it covers, and ends with the key ordering instruction. Every phrase contributes useful context without repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter guide tool with no output schema, the description provides enough context to know it should be called before the action tools. A small gap remains around whether it returns instructions only versus interacting with the Idealista interface itself.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single optional 'task' parameter is fully documented in the schema, including the instruction to describe the desired task in the user's own words. The description does not add any further meaning about how the task influences the returned guidance, so the schema baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states that this is a guide for working in Idealista and names the covered domain areas (listing and updating listings, screens, and the sign-in link). It is clearly distinct from the sibling action tools, though the verb phrase 'How to work' is less specific than a direct verb+resource statement.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Call this first' gives explicit sequencing guidance relative to the sibling tools. It does not describe exclusions or alternatives beyond that first-call instruction, but for a guide tool the main usage guidance is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.