Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_hotels

Search hotels on TripAdvisor by geo ID, then filter by class, amenities, price, Travelers' Choice, currency, and sort or page results.

Instructions

Search TripAdvisor hotels. Searches TripAdvisor hotels in the area given by the required geo_id. Filter with class, amenities, price_min, price_max, pricing_mode, travelers_choice and currency; page with offset and limit; order with sort. Each hotel has its title, URL, image, rating, review count, star rating, rank, price, provider, location and a review snippet when TripAdvisor supplies them.

Input Schema

NameRequiredDescriptionDefault
sortNoSort value
classNoHotel class filter
limitNoMaximum results
geo_idYesTripAdvisor geo id
offsetNoZero-based result offset
currencyNoCurrency code
amenitiesNoAmenity filter ids
filter_idNoOptional filter id such as class or ufe
price_maxNoMaximum price filter
price_minNoMinimum price filter
pricing_modeNoPricing mode
travelers_choiceNoFilter Travelers' Choice properties
travelers_choice_botbNoFilter Best of the Best properties

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / amenities / items
      Added value: +{
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields (title, URL, image, rating, review count, star rating, rank, price, provider, location, snippet) and mentions paging, which is useful, but says nothing about default ordering, result caps, or how geo_id is sourced.

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?

Three sentences, front-loaded with the core action, then parameter roles, then return shape. Dense but well organized with no filler, though the parameter enumeration is long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with no annotations and no output schema, the description does well to summarize both inputs and returns. It remains incomplete on how to obtain geo_id (the autocomplete sibling) and on pagination bounds, which an agent would need.

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 coverage is 100%, so all 13 parameters are already documented in the schema, setting the baseline at 3. The description adds value by grouping parameters into filter / page / order roles, but supplies no formats, allowed values, or units beyond that.

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+resource ('Search TripAdvisor hotels') and scopes it to a geo area, which cleanly separates it from content-oriented siblings like tripadvisor_reviews and tripadvisor_place. It doesn't explicitly name the near-sibling tripadvisor_search, so it falls short of full sibling differentiation.

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?

Gives the required precondition ('in the area given by the required geo_id'), which is genuine usage context. However, it offers no when-to-use/when-not guidance relative to tripadvisor_search, tripadvisor_autocomplete, or other hotel tools, leaving the agent to infer selection.

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