Opens an Idealista page in your signed-in Cloud Browser so you can manage property listings and update prices, descriptions, photos, views, or contacts without an API key.
Open a Idealista page in your signed-in Cloud Browser (default https://www.idealista.com) to work with list and update your listings.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Page to open. Default: https://www.idealista.com |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the authenticated 'signed-in Cloud Browser' context and the default domain, but says nothing about what happens to an already-open page (replace, new tab, navigate), whether session state persists for subsequent click/type calls, or what is returned on success.
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?
A single front-loaded sentence with no boilerplate or repetition. The trailing purpose clause is awkwardly worded ('to work with list and update your listings') but is short enough not to undermine the structure.
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?
This is a simple one-parameter navigation tool with no output schema, so the description needn't explain return values. However, for a browser-session tool it omits how the opened page relates to subsequent sibling operations and what the caller should expect after opening — relevant context that is cheap to include.
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?
There is one optional parameter and schema description coverage is 100%, so the schema already fully documents the url field and its default. The description merely restates the same default URL, adding no format, constraint, or validation meaning beyond the schema.
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 gives a specific verb and resource — 'Open a Idealista page in your signed-in Cloud Browser' — which is clearly distinguishable from siblings like idealista_read, idealista_click, and idealista_close. It does not explicitly name the sibling boundary, and the trailing clause 'to work with list and update your listings' is grammatically garbled and muddies the purpose slightly.
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?
Usage is only implied: the phrase 'to work with list and update your listings' hints that this is the entry point before read/click/type operations. There is no explicit statement of when to call this versus idealista_read or idealista_status, and no prerequisites or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.