Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_hotels

Search TripAdvisor hotels by geo ID, price, class, and amenities; get normalized public listing data for market research, trip planning, and comparison.

Instructions

Search TripAdvisor hotels. Returns normalized TripAdvisor hotel listing results from public credential-free GraphQL listing data.

Input Schema

TableJSON 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.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add some behavioral context: 'public credential-free' signals no auth is required, and 'normalized ... GraphQL listing data' hints at data source and output transformation. However, it does not mention pagination behavior, default ordering, rate limits, or result shape beyond 'listing results'.

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?

Two sentences with the core purpose front-loaded and no redundant filler. It is concise, though a short pointer to related tools would have increased utility without bloating it.

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

Completeness2/5

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

Given 13 parameters, no annotations, no output schema, and several closely related Tripadvisor siblings, this description is incomplete. It does not tell the agent how to supply or discover geo_id, mention the autocomplete companion tool, or describe the normalized return structure, so an agent has too much left to infer.

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 the baseline is 3. The description itself adds no parameter-level meaning, but the schema already documents every parameter, so this is acceptable; no compensation is required.

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?

Description states a specific action and resource: 'Search TripAdvisor hotels' and clarifies the return type ('normalized TripAdvisor hotel listing results'). This is clear enough to distinguish from generic place/search tools, though it never names a sibling such as tripadvisor_search or tripadvisor_place.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus nearby siblings like tripadvisor_search, tripadvisor_place, or tripadvisor_autocomplete. The description does not state conditions, exclusions, or prerequisites (e.g., obtaining geo_id via autocomplete), leaving selection to inference.

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