Retrieve paginated Airbnb reviews guests left for a host, including reviewer name and location. Use host ID and page number to fetch clean review data.
Get Airbnb host reviews. Returns reviews guests left for an Airbnb host, paginated, including the reviewer name and location.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Host id (numeric) | |
| page | No | 1-based page |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. While it mentions pagination and output fields, it omits behavioral details such as sorting order, rate limits, or whether reviews are in reverse chronological order, which are critical for an API tool.
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?
The description is two sentences, front-loads the core purpose, and every sentence adds value without redundancy.
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?
With no output schema, the description should compensate by detailing return structure. It only mentions reviewer name and location, missing essential fields like rating, date, and text. Pagination details (page size, total results) are absent, leaving significant gaps for agent use.
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 description coverage is 100%, so the schema already documents both parameters adequately. The description adds no semantic value beyond confirming pagination context; baseline 3 is appropriate.
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?
The description clearly states the verb 'Get' and resource 'host reviews', explicitly mentions output includes reviewer name and location, and distinguishes from similar sibling tools like airbnb_room_reviews by specifying 'host'.
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 context (when you need host reviews) but does not provide explicit guidance on when to use this tool vs. alternatives like airbnb_room_reviews, nor does it mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.