Skip to main content
Glama

Search Flatio listings

flatio_search_listings
Read-only

Use this when someone wants to rent a furnished flat, house or room for a month or longer and names a city or country, with or without dates, budget, size or pets. It returns up to 10 listings per page with the monthly price and a link to the listing on flatio.com, where the guest books. It takes dates, a budget, a size and pets as filters. Not for nightly or holiday stays, and not for buying property. Give the guest each listing's url exactly as returned, with all its query parameters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "flatio_search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
petsNotrue when a pet moves in.
sortNoOrder of the listings, the same as on flatio.com.recommended
limitNoListings per page, 1 to 10.
cursorNonext_cursor of the previous page, sent with the same filters.
guestsNoPeople moving in, e.g. 2.
monthsNoStay length in months when there are no dates, e.g. 6. Not together with move_in.
move_inNoMove-in date as YYYY-MM-DD, e.g. "2027-02-01". Leave out when the dates are not known.
currencyNoCurrency of max_monthly_price and of every price in the result, e.g. "EUR". Defaults to the currency of the response language's Flatio site.
languageNoLanguage of titles, texts and links, e.g. "en", "cs", "de", "es", "pt". Defaults to the language the client reports, else English.
locationYesCity or country name in any language, e.g. "Lisbon", "Praha", "Portugal". A neighbourhood or an address is not accepted.
move_outNoMove-out date as YYYY-MM-DD, after move_in, e.g. "2027-08-01". Needs move_in.
bedrooms_minNoFewest rooms with a bed, e.g. 2, the same as the bedrooms filter on flatio.com. A living room with a sofa bed counts, so a listing can show fewer bedrooms.
property_typeNoapartment is a whole flat, house a whole house, room a private room in a shared flat.
max_monthly_priceNoHighest monthly rent in the given currency, e.g. 1500.

Output Schema

NameRequiredDescriptionDefault
totalYesAll listings matching the filters, of which at most 100 can be paged.
messageYes
listingsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive behavior, so the added value here is output shape ('up to 10 listings per page with the monthly price and a link'), the fact that booking happens off-tool on flatio.com, and the operational rule to return each url verbatim with all its query parameters. Those are real behaviors not encoded in the annotations or schema. It stops short of mentioning any rate limits or failure modes, which keeps it from 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.

Conciseness5/5

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

Four short sentences, front-loaded with the usage trigger, then the return format, then the exclusions, then the URL-handling rule. Nothing is redundant with the schema, and no sentence could be dropped without losing guidance.

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

Completeness5/5

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

For a 14-parameter tool with full schema coverage, an output schema and read-only annotations, the description supplies exactly what structured fields cannot: audience eligibility (monthly stays only), what a call yields, and the critical instruction to preserve listing URLs verbatim. An agent has everything needed to select and invoke it correctly.

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?

Schema description coverage is 100% and every parameter, including months-vs-move_in exclusivity and the currency/language defaults, is documented in the schema itself. The description only summarizes 'dates, a budget, a size and pets as filters', which adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 names a specific operation on a specific resource family (furnished flat, house or room to rent for a month or longer) and states the trigger input (a city or country, optionally with dates, budget, size, pets). It also draws the boundary against nightly stays and property purchases, so an agent can separate it from a generic search or a single-listing fetch without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use condition ('when someone wants to rent ... for a month or longer and names a city or country') and explicit when-not conditions ('Not for nightly or holiday stays, and not for buying property'). The only thing missing is a named alternative tool, but no such monthly-rental sibling exists in the sibling list supplied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources