Skip to main content
Glama

Livuma — Bali rental & property search

Get listing details

get_listing_details
Read-onlyIdempotent

Returns what the public listing page shows for one listing: description, photos, all rates and minimum stays, amenities and included services, seasonal nightly pricing, published guest reviews, host verification, the booked/blocked calendar and the canonical url. With checkInDate (and checkOutDate, or a rentalMode) the response also includes a live availability quote for those dates.

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": {
      "listingId": "<listingId>"
    },
    "name": "get_listing_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNo"IDR" (default), "USD", or "EUR".
listingIdYesThe listing's "id" from search results (GUID). The short id from a /s/{id} link, or the listing URL itself, also work.
rentalModeNo"dates" (default), "open_ended" or "yearly".
checkInDateNoOptional check-in date, yyyy-MM-dd — adds a live quote for the stay.
checkOutDateNoOptional check-out date, yyyy-MM-dd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context — and it does, by disclosing the conditional response expansion (live availability quote) when date parameters are supplied. It does not mention response size, review pagination, or any rate-limit/permission context, which keeps it short of 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?

Two sentences, front-loaded with the core action and result, followed by the conditional enrichment. The long enumeration of returned fields is dense but every item carries information an agent needs to decide whether this tool answers its question.

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?

With no output schema and five parameters, the description carries the return-value burden and does so thoroughly, including the canonical url and calendar. What is missing is modest: how the large embedded collections (reviews, calendar, rates) are bounded or truncated, and whether authentication is required for host verification data.

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; the description earns above that by explaining the interaction between parameters — that checkInDate together with checkOutDate or a rentalMode triggers a live availability quote. It adds no further meaning for currency or the accepted id formats, which the schema already documents.

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 verb and resource ("Returns what the public listing page shows for one listing") and then enumerates the exact payload: description, photos, rates, minimum stays, amenities, seasonal pricing, reviews, host verification, calendar and canonical url. The phrase "for one listing" plus the required listingId makes it clearly distinct from the search/availability siblings.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the detail-fetch counterpart to search, and the second sentence explains that adding checkInDate (optionally with checkOutDate or rentalMode) enriches the response with a live quote. There is no explicit when-not clause and no named alternative such as check_availability for pure pricing questions.

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.