Otodom MCP

Full details of one otodom.pl listing (or a developer's project page): price, czynsz (rent_extra) and deposit (PLN), price per m², area and plot area, rooms, floor and the building's floor count, year built, building type and material, heating, ownership, condition, windows, energy certificate, availability date, market, address with district and coordinates, seller type and agency name, amenities/equipment as `features`, every other stated attribute in `details`, the full description and photo URLs. Contact phone numbers are not returned. For a development project, `development` gives its unit count, area range and completion date. Get the slug from otodom_search. Fetched live from otodom.pl (typically 0.3–1 s via direct fetch; ~5–10 s when it falls back to an unblocker). Result: { source, fetchedAt, offer: { id, slug, url, title, status, type, transaction, kind, market, price, rent_extra, deposit, price_per_m2, currency, price_on_request, area_m2, plot_area_m2, rooms, floor, floors_in_building, year_built, building_type, building_material, heating, ownership, condition, windows, energy_certificate, available_from, address, location_id, geo, seller_type, agency_name, agency_url, date_created, date_modified, features, details, description, photos, development? } }. Codes such as heating 'urban' (district heating) or condition 'ready_to_use' are Otodom's own. A removed listing is an error that says so.

Search property listings on otodom.pl, Poland's largest real-estate portal: flats, studios, houses, rooms, plots, commercial premises, warehouses, garages and developers' new projects, for sale or for rent. Filter by place (a city, 'city district', town, village or voivodeship, resolved by Otodom's own location search), price, area, rooms, private-owner vs agency listings and primary/secondary market; sort by newest, price or area. Returns one results page (24 by default) with each listing's price, czynsz, price per m², area, rooms, floor, place, seller type and link; pass a listing's `slug` to otodom_offer for full details. Fetched live from otodom.pl (typically 0.3–1 s via direct fetch; ~5–10 s when it falls back to an unblocker). Result shape: { source, fetchedAt, query, search_url, heading, resolved_location, other_locations?, total_count, page, page_size, total_pages, count, listings: [...], note?, warning? } — the list key is `listings`; `total_count` counts matches across all pages (use `page` for more). Each listing: { id, slug, url, title, kind, price, rent_extra, price_per_m2, currency, price_on_request, area_m2, plot_area_m2, rooms, floor, location, street, district, city, region, location_id, seller_type, agency_name, features, is_promoted, date_created, image, photos_count, description, development? }. Prices are numbers in PLN: for rentals `price` is the monthly rent, and `rent_extra` is the monthly administrative fee (czynsz) paid on top (stated on sales too); `price` is null with price_on_request true when the advertiser hides it. `floor` is 'ground', '1'…'10', '10+', 'basement' or 'attic'. `kind` is 'new_development' for a developer's project (its units' ranges in `development`), else 'listing'; `seller_type` is private | agency | developer. `resolved_location` says which place was searched — check it; `other_locations` lists other matches for the name (pass one's `id` as `location`). An empty match answers count: 0 with a `note` saying why and what to change — that is a successful result, not an error.