Problem
rightmove_search with default sort returns results ordered by Rightmove's own prominence/featured algorithm, which heavily favours premium-priced listings. This means a subject property at the lower end of the local price range may not appear at all in the default 25-result page.
Real example
Searching near DE73 8AU (Breedon on the Hill) with radius=2 and no price filter returned 25 listings ranging from £190,000 to £1,750,000 — with the majority between £600k–£1.1M. The subject property (9 Hollow Road, £290,000) was not in the results despite being an active listing at the same postcode.
It only appeared when re-running with max_price=350000 and radius=0.5.
Impact
When using rightmove_search to find a specific subject property (Lane A in the property-report skill), the default sort is unreliable. An LLM following the skill workflow may conclude the property isn't listed when it simply wasn't ranked into the top 25.
Suggested fix
Either:
- Default
sort_by to price_low so lower-priced properties appear first in mixed-stock areas
- Add a
find_listing(address, postcode) helper that searches specifically for a named address rather than relying on rank
- Document clearly that the default sort is Rightmove prominence and recommend
sort_by=price_low when searching for a specific subject property
Option 2 would be the most robust — a direct address lookup rather than relying on search ranking.
Problem
rightmove_searchwith default sort returns results ordered by Rightmove's own prominence/featured algorithm, which heavily favours premium-priced listings. This means a subject property at the lower end of the local price range may not appear at all in the default 25-result page.Real example
Searching near DE73 8AU (Breedon on the Hill) with
radius=2and no price filter returned 25 listings ranging from £190,000 to £1,750,000 — with the majority between £600k–£1.1M. The subject property (9 Hollow Road, £290,000) was not in the results despite being an active listing at the same postcode.It only appeared when re-running with
max_price=350000andradius=0.5.Impact
When using
rightmove_searchto find a specific subject property (Lane A in the property-report skill), the default sort is unreliable. An LLM following the skill workflow may conclude the property isn't listed when it simply wasn't ranked into the top 25.Suggested fix
Either:
sort_bytoprice_lowso lower-priced properties appear first in mixed-stock areasfind_listing(address, postcode)helper that searches specifically for a named address rather than relying on ranksort_by=price_lowwhen searching for a specific subject propertyOption 2 would be the most robust — a direct address lookup rather than relying on search ranking.