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

TableJSON 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

TableJSON 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 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.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. Beyond that, the description adds real behavior: sort order, fields carried per listing, the location_not_found error surfaced as zero results, and exclusion of 'price on application' listings. Some of this (returned fields) overlaps the output schema, so it is not a 5.

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-loads the core definition, then ordering, then usage, then filter/edge-case behavior. Every sentence carries information, though the 'Each listing carries...' enumeration leans slightly verbose given an output schema exists.

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?

For a 9-parameter, zero-required read tool with annotations and an output schema, the description covers purpose, ordering, usage, filter inheritance, and key edge cases (location_not_found, P.O.A. exclusion). Nothing critical is missing, though pagination/limit behavior is left entirely to the schema.

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?

At 67% schema coverage, the schema documents days/limit/min_percent/search_type but the description adds a useful cross-reference ('filters work as in search_properties') tying location/type/bedrooms/price semantics to a sibling tool, plus the location_not_found edge case. It does not add syntax detail, so it stays above baseline without being exhaustive.

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 verb+resource: 'Live listings whose asking price has been reduced recently', plus the display ordering ('biggest reduction first'). An agent can immediately distinguish this from search_properties or find_similar_properties without opening any schema.

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?

Provides concrete use-case framing ('what has dropped in price in Estepona this month?', 'to spot motivated sellers') and notes filters behave as in search_properties. It stops short of naming a sibling to prefer instead or stating explicit when-not-to-use conditions, so it is strong context but not full routing guidance.

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?