Skip to main content
Glama

Read a Tripadvisor hotel

tripadvisor_hotel

Read one Tripadvisor hotel page -- address, ranking, rating and subratings, amenities, offers and prices, nearby places and the first page of reviews. Takes the hotel url, e.g. from a tripadvisor_search result. Spends a flat number of credits, refunded if the page could not be read. If status is "queued" or "running", call crawl_poll with the job_id to collect it.

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": {
      "url": "<url>"
    },
    "name": "tripadvisor_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Tripadvisor hotel page, e.g. https://www.tripadvisor.com/Hotel_Review-g187497-d190607-Reviews-Hotel_Name-Barcelona_Catalonia.html, from any of Tripadvisor's country sites. It is read on the English site.
cityNoThe city inside that country to appear to browse from, as the pool spells it: letters, digits, hyphens or underscores, e.g. berlin or new_york. Requires country. Doubles the price of the crawl.
countryNoThe country to appear to browse from, as a two-letter ISO 3166-1 code such as es, us or de. Free. Required to use city.
premiumNoFetch through the premium proxy pool instead of the standard one. Costs more; use it for targets that refuse ordinary requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, the description discloses the cost model (flat credits), refund behavior for unread pages, asynchronous status handling, and the limited review scope (first page only). These are important behavioral details an agent would not know from the annotations alone.

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?

The description is front-loaded with what is read and its scope, then follows with URL sourcing, credit/refund behavior, and async polling instructions. Every sentence contributes useful operational information without redundancy.

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?

For a read tool with four parameters and no output schema, the description covers the returned content, source URL, cost/refund behavior, and polling path. It could say more about the response shape when a job is queued, but it is otherwise sufficient for correct invocation.

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 explains URL, city, country, and premium parameters thoroughly. The description adds only source context for the URL, not new meaning for the geo or premium parameters, matching the baseline 3.

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?

The description states a specific verb and resource: read one Tripadvisor hotel page, then enumerates the exact content returned. It also distinguishes the tool from tripadvisor_search by saying it takes a hotel URL, typically from a search result.

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?

It gives clear operational context: use a Tripadvisor hotel URL, and if status is queued or running, call crawl_poll with job_id. It does not explicitly state when not to use this tool or directly compare it with booking_hotel, so it falls short of full alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources