PropertyList: Spanish Property MLS

Save a search with email alerts

save_search

Save a property search on PropertyList for a person, with email alerts when new listings match. Takes the same filters as search_properties (location or location_id, search_type, property_types, bedrooms, bathrooms, price, the pool feature). The person must confirm by email: PropertyList emails them a link, and the search is saved (and their free PropertyList account made, or opened, with no password) only when they open it. Tell them to check their email. Ask for their email address and whether they want alerts (daily, weekly by default, every two weeks, monthly, or none). Filters saved searches cannot hold are listed in not_kept. To see, change or delete saved searches later, use manage_saved_searches.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "save_search"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Optional. The person's name.
`email`	Yes	The person's email address; the confirmation link goes to it.
`tenure`	No	Commercial sales only: business transfers.
`features`	No	pool is kept; other features are not, and come back in not_kept.
`language`	No	The person's language, for the email and the alerts.	en
`location`	No	Place name, as in search_properties.
`price_max`	No
`price_min`	No
`location_id`	No	Area id from autocomplete_location. Takes precedence over location.
`search_type`	No	Defaults to 'for-sale'.
`bedrooms_max`	No
`bedrooms_min`	No
`bathrooms_min`	No
`property_types`	No	One slug, as in search_properties (apartments, villas, penthouses, townhouses, plots, country-houses, commercial or a commercial page such as offices). Several types save as all homes.
`alert_frequency`	No	How often new matches are emailed; none saves it without alerts.	weekly

Output Schema

Name	Required	Description
`email`	Yes
`status`	Yes
`summary`	Yes	The search as it will be saved.
`not_kept`	No	Filters a saved search cannot hold.
`alert_frequency`	No
`expires_in_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses the critical double opt-in workflow: the person is emailed a link, the search is only saved after they open it, and an account may be created or opened without a password. It also explains alert frequency defaults, the none option, and that unsupported filters come back in not_kept.

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

Conciseness5/5

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

The purpose is stated in the first sentence, followed by the key confirmation workflow, alert choices, and sibling routing. Despite covering a multi-step operation, every sentence carries operational value and there is no filler.

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

Completeness5/5

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

For a 15-parameter tool with a confirmation workflow, the description covers what an agent must know: required email, when the search actually saves, account creation behavior, alert options, filter limitations, and where to manage saved searches later. An output schema exists, so return-value details need not be repeated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema description coverage and 15 parameters, the description adds useful semantics: it says the filters mirror search_properties, explains the email's role, describes alert_frequency options including the weekly default, and notes that unsupported filters appear in not_kept. Several filter parameters still rely on the schema or the search_properties shorthand, so it does not fully document every parameter.

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

Purpose5/5

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

The description states a specific verb and resource: saving a property search for a person with email alerts. It distinguishes the tool from search_properties by framing it as saving filters and from manage_saved_searches by naming that sibling for later viewing, changing, or deleting.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It makes clear that this is for persisting a search with alerts, references search_properties for the filter vocabulary, and sends later management to manage_saved_searches. It stops short of an explicit when-not-to-use statement, so it is strong but not fully exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PropertyList: Spanish Property MLS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?