Skip to main content
Glama

Airbnb stays for a place and dates: listing id, name, type

travel_airbnb
Read-only

Airbnb stays for a place and dates (first results page, usually 18): listing id, name, type, total price for the stay in the chosen currency (and original price when discounted), rating out of 5 with review count, beds/bathrooms, badges such as Guest favourite, free-cancellation note, coordinates and room URL. From Airbnb's public search page; availability and prices as Airbnb shows them at call time. Related tools on this server, for a different need: travel_agoda when you need top hotels in a city from Agoda's city guide page: about 10; travel_hostelworld when you need Hostels in a city as listed on Hostelworld's public city. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "travel_airbnb"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNoAdults, 1 to 16 (default 1)
checkinNoCheck-in date YYYY-MM-DD (optional; Airbnb picks flexible dates without it)
checkoutNoCheck-out date YYYY-MM-DD (needed with checkin)
currencyNoThree-letter currency code (default USD)
locationYesPlace, e.g. 'Paris, France' or 'Austin, TX'

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
checkinNo
checkoutNo
currencyNo
listingsNo
locationNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses that results come from Airbnb's public search page, that it returns only the first results page (usually ~18), and that availability and prices reflect what Airbnb shows at call time. It also states the cost model ($0.002 per successful call, x402/USDC on Base, Solana and 10+ networks) and that failed calls are not charged — exactly the billing and freshness context an agent needs.

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 the core purpose and returned fields before moving to source/freshness, alternatives, and pricing, in a single readable paragraph. The field enumeration is long but every clause carries information an agent would otherwise have to guess; little is 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?

Despite an output schema existing (which would excuse omitting return details), the description still summarizes the payload shape, result count, data provenance, freshness, cost and sibling alternatives. Nothing material is missing for an agent to decide to call it and interpret the response.

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 coverage is 100%, so the schema already documents location, dates, adults and currency. The description only reinforces that price is returned 'in the chosen currency' and that results are for a place and dates; it adds no format or behavioral nuance (e.g. what happens when checkout is missing) beyond the schema. Baseline 3 for full coverage 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?

States a specific verb and resource ('Airbnb stays for a place and dates') and enumerates the returned fields (listing id, name, type, total price, rating, beds/baths, badges, coordinates, room URL). Siblings travel_agoda and travel_hostelworld are named with the distinct needs they serve, so an agent can tell the three apart without opening any 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?

Explicitly routes the agent elsewhere: travel_agoda for top hotels from Agoda's city guide page (~10) and travel_hostelworld for hostels in a city. This gives clear when-to-use-other guidance, though it doesn't state a when-not-to-use condition for this tool itself (e.g. no availability filtering, no full inventory).

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