PropertyList: Spanish Property MLS

Find price reductions

find_price_reductions

Read-onlyIdempotent

Live listings whose asking price has been reduced recently, biggest reduction first. Each listing carries the price before the cut, the price now, the reduction in euros and percent, and when it was cut. Use for "what has dropped in price in Estepona this month?" or to spot motivated sellers.

Filters work as in search_properties (location, type, bedrooms, price). A location we do not hold returns zero results with error: location_not_found. Listings shown as price on application are never included.

Input Schema

Name	Required	Description	Default
`days`	No	How far back to look for reductions.
`limit`	No
`language`	No		en
`location`	No	Place name, e.g. 'Marbella'. Omit for every area.
`price_max`	No	Maximum CURRENT price in euros (sale) or monthly euros (rent).
`min_percent`	No	Only reductions of at least this percentage.
`search_type`	No	Defaults to 'for-sale'.
`bedrooms_min`	No
`property_types`	No	Comma-separated slugs: apartments, villas, penthouses, plots, townhouses, or commercial (every commercial type; office, shop, restaurant, hotel, warehouse and the other commercial types also work alone). Without it the search covers homes only.

Output Schema

Name	Required	Description
`days`	No
`error`	No
`total`	Yes
`limits`	No
`properties`	Yes
`history_from`	No	Earliest date we hold price history for.
`location_match`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedOutput schema / properties / properties / items / properties / buildable_sqm
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / property_types / description

Previous value: -"Comma-separated slugs: apartments, villas, penthouses, plots, townhouses, commercial."New value: +"Comma-separated slugs: apartments, villas, penthouses, plots, townhouses, or commercial (every commercial type; office, shop, restaurant, hotel, warehouse and the other commercial types also work alone). Without it the search covers homes only."

Changed1 schema field changedOct 13, 2026
- addedOutput schema / properties / limits
```
Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
```
AddedOct 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's job is to add operational detail — and it does: result ordering, the per-listing return fields, the location_not_found error contract, and the exclusion of price-on-application listings. It doesn't mention corpus freshness or pagination, but the essential behaviors are disclosed.

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

Conciseness4/5

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

Front-loaded with the defining sentence, then example queries, then filter/error/exclusion notes. Slightly dense and the line breaks are odd, but every sentence carries information.

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

Completeness4/5

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

An output schema exists, so return values needn't be explained — and yet the description still names the key fields, which helps. The filter model is delegated to a sibling and the error contract is stated, leaving only minor gaps around defaults and result caps.

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?

The schema covers 67% of parameters, and the description adds the useful rule that filters behave like search_properties and that an unknown location returns an error. However, it says nothing about days, limit, language, or min_percent beyond the schema, and those undocumented parameters remain undocumented in both places.

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?

States a specific resource and a specific cut of the data: live listings with a reduced asking price, sorted biggest reduction first. This is clearly distinguishable from search_properties, which it explicitly references only for filter semantics.

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?

Gives two concrete use cases ('what has dropped in price in Estepona this month?' and spotting motivated sellers) and points to search_properties for the general filter model. It doesn't explicitly say when not to use this tool (e.g. for unsold inventory without a cut), but the intent is clear enough.

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?