Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

tripadvisor_search

Search TripAdvisor places by geo ID and type to get normalized listings for hotels, restaurants, and attractions, with filters for price, class, and dates.

Instructions

Search TripAdvisor places. Returns normalized TripAdvisor place listings for hotels, restaurants, attractions, and supported attraction category types.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort value
`type`	Yes	Listing type
`class`	No	Hotel class filter
`limit`	No	Maximum results
`geo_id`	Yes	TripAdvisor geo id
`locale`	No	TripAdvisor locale
`offset`	No	Zero-based result offset
`currency`	No	Currency code
`amenities`	No	Hotel amenity filter ids
`filter_id`	No	Optional hotel filter id
`price_max`	No	Maximum hotel price filter
`price_min`	No	Minimum hotel price filter
`pricing_mode`	No	Hotel pricing mode
`online_options`	No	Restaurant online option ids
`restaurant_date`	No	Restaurant availability date
`restaurant_time`	No	Restaurant availability time
`travelers_choice`	No	Filter Travelers' Choice hotels
`restaurant_guests`	No	Restaurant guest count
`establishment_types`	No	Restaurant establishment type ids
`travelers_choice_botb`	No	Filter Best of the Best hotels

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / amenities / items
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / properties / establishment_types / items
```
Added value: +{
+  "type": "integer"
+}
```
- addedInput schema / properties / online_options / items
```
Added value: +{
+  "type": "integer"
+}
```
First observedv1.0.0Jun 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It states the tool returns normalized listings, which implies a read-only search and provides some output expectation. However, it does not disclose pagination behavior, rate limits, default sorting, or how the 'normalized' transformation works, leaving meaningful behavior unstated.

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 two sentences with no wasted words. The first sentence states the core purpose, and the second adds the key output detail about supported listing categories. Information is front-loaded and efficient.

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?

This is a 20-parameter tool with no annotations and no output schema, yet the description only gives a one-line overview. It does not explain that many parameters are hotel- or restaurant-specific, how to source geo_id (e.g., via tripadvisor_autocomplete), or what 'normalized' listings look like. An agent would struggle to invoke this correctly for a specific use case without deeper investigation.

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 baseline is 3. The description adds no parameter-level meaning beyond the schema's terse comments (e.g., 'Sort value', 'Listing type'). It does not clarify how parameters group by listing type (hotel vs restaurant vs attraction), which would help an agent select appropriate filters.

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?

The description states a clear action (Search TripAdvisor places) and resource (place listings) and enumerates the covered categories (hotels, restaurants, attractions). It does not explicitly differentiate from sibling tools such as tripadvisor_hotels or tripadvisor_place, though the scope of 'normalized listings' implies a broad search rather than a detail or hotel-specific endpoint.

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 is provided on when to use this tool versus alternatives like tripadvisor_hotels, tripadvisor_place, or tripadvisor_autocomplete. The description does not mention required inputs, prerequisites (e.g., obtaining a geo_id), or scenarios where one sibling should be preferred. This leaves the agent to infer usage solely from the tool name.

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

Deploy Server

tripadvisor_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools