Retrieve public Airbnb guest reviews for a room by ID, one page at a time, including author, date, rating, and text.
Get Airbnb room reviews. Returns public guest reviews for one Airbnb room by room id, one page at a time (page is 1-based). Each review has the author, date, rating and text. Reviews are returned only when Airbnb exposes them for the listing.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Room id | |
| page | No | 1-based page |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses pagination semantics (1-based, one page at a time) and the caveat that 'reviews are returned only when Airbnb exposes them for the listing', which is real behavioral context. It omits whether a total count or end-of-pagination signal exists, so paging behavior remains partly opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no filler, front-loaded with the core purpose followed by pagination and fields. The return-field inventory is slightly redundant but still concise overall.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 2-param read tool with no output schema, the description covers what each review contains and the pagination model, which is adequate. It stops short of explaining how to know when reviews are exhausted or how many pages exist, leaving a gap for an agent driving the pagination loop.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both parameters are already documented. The description restates that 'page' is 1-based (matching the schema) and clarifies 'id' refers to a room id, adding only marginal meaning beyond what the schema already provides. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get Airbnb room reviews... public guest reviews for one Airbnb room by room id'), so an agent immediately knows the resource and the keying parameter. It does not explicitly distinguish itself from the sibling airbnb_host_reviews, which is the main ambiguity an agent faces here.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by requiring a room id and noting results come 'one page at a time', so context is inferable. However, it never states when to prefer this over airbnb_host_reviews or how paging should proceed across calls, leaving routing and usage to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.