Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

airbnb_host_reviews

Retrieve Airbnb host reviews by numeric host ID and page to inspect guest ratings, comments, dates, and reviewer locations.

Instructions

Get Airbnb host reviews. Returns the reviews guests left for an Airbnb host, identified by the numeric host id. page is 1-based (default 1). Each review has its id, rating, comments, created_at, reviewer name and reviewer_location, and has_more says whether another page follows.

Input Schema

NameRequiredDescriptionDefault
idYesHost id (numeric)
pageNo1-based page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return shape (id, rating, comments, created_at, reviewer, reviewer_location) and pagination behavior (1-based page, has_more flag), but says nothing about auth requirements, rate limits, or whether reviews are read-only in a stated sense—though 'Get/Returns' implies a read.

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 purpose, then target identification, then pagination and return fields. Efficient with no filler, though the return-field enumeration is slightly listy.

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 no annotations, the description usefully compensates by enumerating the returned fields and pagination semantics. It leaves only minor gaps such as auth and error behavior.

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 description coverage is 100%, so both parameters (id, page) are already documented. The description restates 'page is 1-based (default 1)' and that id is numeric, adding only marginal clarification beyond the schema—the baseline 3 for fully-covered params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Airbnb host reviews') and clarifies the target is a host identified by numeric id, which distinguishes it from the sibling airbnb_room_reviews. It stops short of explicitly naming that sibling, so an agent must infer the host-vs-room distinction.

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 only implied: the description says reviews are fetched for a given host id, but gives no explicit when-to-use guidance or contrast with airbnb_room_reviews or airbnb_host. Adequate but with a clear gap.

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