Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

airbnb_room

Fetch public details for an Airbnb listing by room ID, including title, location, capacity, amenities, pricing, rating, reviews, and host flags.

Instructions

Get Airbnb room. Returns the public details of one Airbnb listing by room id: title, description, property type, location and coordinates, guest capacity, amenities, price and price per night, rating, review count, host, and the Superhost and Guest Favorite flags. Some fields are present only when Airbnb exposes them for the listing.

Input Schema

NameRequiredDescriptionDefault
idYesRoom id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: 'Some fields are present only when Airbnb exposes them for the listing,' warning the agent that return content is variable. It does not state failure modes (invalid/missing id) or rate/permission behavior, but for a low-risk read operation this is solid coverage.

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-loads the verb+resource in the first clause, then lists return fields, then adds the caveat. Efficient and well-ordered, though the field enumeration is somewhat long relative to the trivial input.

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?

No output schema exists, so the description must document the return surface — and it does, listing title, description, property type, location, capacity, amenities, pricing, rating, reviews, host, and flags. Nothing an agent needs to call this correctly is missing.

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% and there is a single 'id' parameter already documented as 'Room id.' The description reinforces that the id is a room/listing identifier but adds no format, example, or sourcing guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (get a single Airbnb listing by room id) and enumerates the returned fields, making clear this is a detail lookup rather than the sibling airbnb_search list endpoint. An agent can distinguish it from airbnb_room_reviews or airbnb_room_calendar 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 Guidelines3/5

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

The 'by room id' phrasing implies usage (fetch details for a known listing), but there is no explicit when-to-use, when-not-to-use, or reference to alternatives like airbnb_search for discovery. Usage is inferable but not spelled out.

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

Deploy Server

Other Tools