Skip to main content
Glama

Livuma — Bali rental & property search

Search listings

search_listings
Read-onlyIdempotent

Searches Livuma's live Bali rental and property-sale inventory with the same results, filters and prices as the livuma.com search page. Returns { items, page, pageSize, total, hasMore, filteredAfterPaging }. Each item has the canonical url, the primary photo, the price for this search (the stay total when dates are given, otherwise the per-period rate), the host's rates and minimum stays, amenities, rating, coordinates and isBookable. total is the number of database matches. When filteredAfterPaging is true, the exact per-stay price was applied after paging, so a page can hold fewer items than pageSize while hasMore is still true. One area is searched per request. Search results are not a booking quote: availability, the applicable rate and the exact price are confirmed only by the availability check for specific dates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOne area name, e.g. "Canggu". Free text, geocoded server-side.
pageNo1-based page number.
offerNo"rent" or "sale". Omit for both.
currencyNo"IDR" (default), "USD", or "EUR".
latitudeNoCenter latitude for coordinate-based location filtering (use with longitude; alternative to area).
maxPriceNoBudget in `currency`, compared against the price shown for this search: the stay TOTAL when check-in and check-out are given, otherwise the monthly rate (yearly in yearly mode) or the asking price for sales.
minPriceNoMinimum budget in `currency`, same unit rules as maxPrice.
minRoomsNoMinimum number of bedrooms.
pageSizeNoResults per page, 1-100 (default 20).
amenitiesNoAmenity filters, e.g. ["pool","wifi","pet_friendly"].
longitudeNoCenter longitude for coordinate-based location filtering (use with latitude).
excludeIdsNoListing GUIDs to exclude, e.g. results already shown to the user.
rentalModeNoHow a rental stay is priced: "dates" (default — give checkInDate + checkOutDate, or neither to browse monthly rates), "open_ended" (checkInDate only, monthly rate, no end date), "yearly" (checkInDate only, fixed 12-month term).
checkInDateNoCheck-in date, yyyy-MM-dd.
areaRadiusKmNoSearch radius in km around the area or the coordinates (default 10, max 20).
checkOutDateNoCheck-out date, yyyy-MM-dd. Omit for open_ended and yearly.
propertyTypeNoProperty type name, e.g. "Villa", "Apartment".
ownershipTypeNoOwnership type for sales, e.g. "Freehold". Not used for rentals.
includeInsightsNoInclude AI-extracted photo and description insights. Off by default — they are large.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description adds real substance on top: the exact return envelope, the meaning of `total` versus page contents, and the `filteredAfterPaging` quirk that can yield short pages while `hasMore` stays true. It also warns that results are not a quote, which is a behavioral caveat no annotation conveys.

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-loaded with purpose, then return shape, then paging caveat, then the quote disclaimer — a sensible ordering. It is dense with backtick-heavy field names and a couple of clauses ('One area is searched per request') that could be tightened, but no sentence is truly wasted.

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 19-parameter, zero-required search tool with no output schema, the description carries the necessary weight: it documents the return envelope, per-item fields, pricing semantics, paging edge case, and the availability caveat. An agent has everything needed to call it correctly and interpret the response.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning: the price unit depends on whether dates are given (stay total vs per-period rate), which is exactly what maxPrice/minPrice compare against, and it reinforces area-versus-coordinates as mutually exclusive location modes. This exceeds restating the schema.

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 and resource ('Searches Livuma's live Bali rental and property-sale inventory'), names the source of truth (livuma.com search page), and distinguishes itself from the availability check by noting results are not a booking quote. An agent can tell it apart from check_availability and get_listing_details without opening a 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?

Gives clear operating context: one area per request, dates optional, and an explicit hand-off to the availability check for confirmed pricing. It stops short of naming when to prefer get_search_options for discovering valid areas or get_listing_details for a single listing, so the alternative routing is only partial.

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.