Crawlora MCP

tripadvisor_hotels

Read-only

Search TripAdvisor's public hotel listings and return normalized hotel records. Use tripadvisor_autocomplete to resolve a destination or tripadvisor_place for details about one known place.

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": {
      "geo_id": "<geo_id>"
    },
    "name": "tripadvisor_hotels"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order. Allowed values: BEST_VALUE, POPULARITY. Default BEST_VALUE.
`class`	No	Optional hotel star class filter. Allowed values: 1, 2, 3, 4, 5.
`limit`	No	Max number of hotels to return.
`geo_id`	Yes	Required. TripAdvisor geo id of the location to list hotels for, e.g. 294217.
`offset`	No	Result offset for pagination, default 0.
`currency`	No	Currency code for prices, e.g. HKD, USD, EUR.
`amenities`	No	Optional repeated hotel amenity ids to filter by, e.g. 9176.
`filter_id`	No	Optional filter id. Allowed values: class, ufe.
`price_max`	No	Optional maximum nightly price filter; zero or positive and >= price_min.
`price_min`	No	Optional minimum nightly price filter; zero or positive.
`pricing_mode`	No	Optional pricing mode. Allowed values: ALL_IN_RATE.
`travelers_choice`	No	When true, limit results to Travelers Choice hotels.
`travelers_choice_botb`	No	When true, limit results to Travelers Choice Best of the Best hotels.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and open-world nature are covered. The description adds only the 'normalized hotel records' return note; it discloses nothing about pagination via offset/limit, pricing/availability caveats, or rate limits that a hotel listing tool would plausibly need.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action, followed immediately by the routing guidance. Zero filler and nothing extraneous.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Purpose and routing are complete, but for a 13-parameter search tool it could do slightly more to guide parameter intent (e.g. sort/price filtering).

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 the schema already documents all 13 parameters including geo_id format and enum-like allowed values. The description adds no meaning beyond the schema, which is the correct baseline 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+resource ('Search TripAdvisor's public hotel listings') and adds the return shape ('normalized hotel records'). It also names the sibling tools it is not, letting an agent distinguish tripadvisor_hotels from tripadvisor_autocomplete and tripadvisor_place 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?

Gives an explicit prerequisite route: use tripadvisor_autocomplete to resolve a destination, and tripadvisor_place for details on one known place. It does not, however, differentiate this tool from the sibling tripadvisor_search, which is a notable omission given both are search tools.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.