booli-mcp

Search Booli for-sale listings

booli_search_listings

Read-only

Search active for-sale property listings on booli.se by location or area ID, with filters for price, rooms, living area, object type, and more. Returns paginated results.

Instructions

Search active for-sale property listings on booli.se. Scope by area_id (from booli_search_areas) or a free-text location, and filter by price, rooms, living area, plot, object type, construction year. Paginated by page; check total_count/pages. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`sort`	No	Sort key (default: newest published).
`view`	No	Response shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim PropertySummary/detail projection; "full" returns Booli's whole GraphQL node.
`area_id`	No	Booli area id from booli_search_areas. Provide this OR `location`.
`location`	No	Free-text place name (e.g. "Nacka", "Södermalm") resolved to its top Booli area. Ignored when `area_id` is set.
`ascending`	No	Sort ascending (default false).
`max_rooms`	No
`min_rooms`	No
`object_type`	No	Property type(s), comma-separated, from: Lägenhet, Villa, Kedjehus-Parhus-Radhus, Fritidshus, Gård, Tomt/Mark.
`max_plot_area`	No	m²
`min_plot_area`	No	m²
`max_list_price`	No	SEK
`min_list_price`	No	SEK
`max_living_area`	No	m²
`min_living_area`	No	m²
`max_list_sqm_price`	No	SEK/m²
`min_list_sqm_price`	No	SEK/m²
`is_new_construction`	No	true = only new production; false = exclude new production.
`max_construction_year`	No
`min_construction_year`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Sep 18, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv1.3.1Sep 10, 2026

removedInput schema / properties / compact

Removed value: -{
-  "description": "Return slim summary records (default true). Set false for full raw fields.",
-  "type": "boolean"
-}

addedInput schema / properties / view

Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim PropertySummary/detail projection; \"full\" returns Booli's whole GraphQL node.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}

Changed13 schema fields changedv1.0.0Jul 14, 2026

changedInput schema / properties / area_id / description

Previous value: -"Booli area id(s) from booli_search_areas, comma-separated for several (e.g. \"76,16\")."New value: +"Booli area id from booli_search_areas. Provide this OR `location`."

addedInput schema / properties / ascending

Added value: +{
+  "description": "Sort ascending (default false).",
+  "type": "boolean"
+}

removedInput schema / properties / bbox

Removed value: -{
-  "description": "Bounding box \"lat_lo,lng_lo,lat_hi,lng_hi\" (SW then NE corner).",
-  "type": "string"
-}

removedInput schema / properties / center

Removed value: -{
-  "description": "Coordinate \"lat,lng\" (e.g. \"59.34674,18.0603\"); use with `dim`.",
-  "type": "string"
-}

removedInput schema / properties / dim

Removed value: -{
-  "description": "Rectangle size in metres \"w,h\" (e.g. \"400,500\"), used with `center`.",
-  "type": "string"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Default 30, max 100.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / location

Added value: +{
+  "description": "Free-text place name (e.g. \"Nacka\", \"Södermalm\") resolved to its top Booli area. Ignored when `area_id` is set.",
+  "type": "string"
+}

removedInput schema / properties / max_rent

Removed value: -{
-  "description": "SEK/month",
-  "minimum": 0,
-  "type": "number"
-}

changedInput schema / properties / object_type / description

Previous value: -"Property type(s), comma-separated, from: villa, lägenhet, gård, tomt-mark, fritidshus, parhus, radhus, kedjehus."New value: +"Property type(s), comma-separated, from: Lägenhet, Villa, Kedjehus-Parhus-Radhus, Fritidshus, Gård, Tomt/Mark."

removedInput schema / properties / offset

Removed value: -{
-  "description": "Pagination offset.",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page (default 1).",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / properties / q

Removed value: -{
-  "description": "Free-text area search (e.g. \"Nacka\", \"Södermalm\"). One of q / area_id / center / bbox scopes the search.",
-  "type": "string"
-}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort key (default: newest published).",
+  "enum": [
+    "published",
+    "listPrice",
+    "listSqmPrice",
+    "rooms",
+    "livingArea",
+    "rent",
+    "plotArea"
+  ],
+  "type": "string"
+}

First observedv0.0.0Jul 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this with 'Read-only.' It adds behavioral context beyond annotations by describing pagination ('Paginated by `page`; check `total_count`/`pages`') and the scoping rule ('area_id ... OR location'). No contradictions; the description complements the annotations with operational detail.

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?

Two sentences, no wasted words. The purpose is stated first, then scoping, then filters, then pagination. Every clause earns its place. The structure is front-loaded with the most important information and reads naturally.

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 20-parameter search tool with no output schema, the description covers the core behaviors: what it searches, how to scope, what filters exist, and how pagination works. It references a sibling for area_id resolution. It doesn't mention authentication or rate limits, but those are not essential for selection. The description is sufficient for an agent to call it correctly.

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?

Schema description coverage is 80%, so the baseline is 3. The description adds value by explaining the relationship between area_id and location (location ignored when area_id is set), and by grouping filters by category (price, rooms, living area, etc.). It also clarifies that area_id comes from booli_search_areas, which is not in the schema. This goes beyond the schema's per-parameter descriptions, warranting a 4.

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 opens with a precise verb+resource: 'Search active for-sale property listings on booli.se.' It distinguishes itself from siblings by the 'active for-sale' qualifier, which sets it apart from booli_search_sold (sold listings), booli_get_listing (single listing), and the others. An agent can tell exactly what this tool does and when to reach for it.

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?

The description gives clear context: it's for active for-sale listings, and it even references booli_search_areas for obtaining area_id. It implies the 'when' (when you need active listings) but does not explicitly state exclusions like 'use booli_search_sold for sold listings.' However, the 'active' qualifier and the sibling names make the usage boundary evident, so it's clear enough without being exhaustive.

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

Deploy Server

Search Booli for-sale listings

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools