Crawlora MCP

tripadvisor_search

Read-only

Search TripAdvisor places by keyword or location. Results contain normalized place listings and IDs; use this to discover hotels, attractions, or restaurants before requesting a place detail.

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>",
      "type": "<type>"
    },
    "name": "tripadvisor_search"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order. Allowed values: POPULARITY (all types), BEST_VALUE (hotels only). Default POPULARITY, or BEST_VALUE for hotels.
`type`	Yes	Required listing type. Allowed values: hotel, restaurant, attraction, all, plus attraction category types from tripadvisor.enums.
`class`	No	Optional hotel star class filter. Allowed values: 1, 2, 3, 4, 5.
`limit`	No	Max number of places to return.
`geo_id`	Yes	Required. TripAdvisor geo id of the location to list places for, e.g. 294217.
`locale`	No	Locale code, e.g. en-HK, en-US, en-GB.
`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 price filter; zero or positive and >= price_min.
`price_min`	No	Optional minimum price filter; zero or positive.
`pricing_mode`	No	Optional pricing mode. Allowed values: ALL_IN_RATE.
`online_options`	No	Optional repeated restaurant online-option ids to filter by, e.g. 20693.
`restaurant_date`	No	Restaurant availability date in YYYYMMDD or YYYY-MM-DD format.
`restaurant_time`	No	Restaurant availability time in HHMM or HH:MM 24-hour format.
`travelers_choice`	No	When true, limit results to Travelers Choice places.
`restaurant_guests`	No	Restaurant party size; must be between 1 and 20.
`establishment_types`	No	Optional repeated restaurant establishment-type ids to filter by, e.g. 10591.
`travelers_choice_botb`	No	When true, limit results to Travelers Choice Best of the Best places.

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 5, 2026

TDQS

A3.8/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 is covered. The description adds that results are 'normalized place listings and IDs', which hints at the output shape and the discovery workflow, but says nothing about pagination (an offset param exists) or result bounding (a limit param exists).

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 short sentences with the discovery use case front-loaded and the follow-up pointer at the end. Efficient, though the 'keyword' phrasing is a small inaccuracy given the schema has no keyword field.

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

Completeness5/5

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

For a search tool with a full output schema and 100% parameter coverage, the description only needs to convey purpose and workflow position, which it does. Return values need not be explained because the output schema exists.

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 20 parameters in detail. The description adds only workflow framing and no syntax, defaults, or constraints for fields like sort, type, or the price/date filters. Baseline 3 applies when the schema carries the parameter burden.

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 and resource ('Search TripAdvisor places') and names the content it returns (hotels, attractions, restaurants), which distinguishes it from the detail-oriented siblings. The phrase 'by keyword or location' is slightly loose since the required inputs are geo_id and type rather than a keyword, but the intent is clear.

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?

Explicitly positions the tool as a discovery step that precedes 'requesting a place detail', effectively routing the agent to tripadvisor_place for follow-up. It stops short of acknowledging the other siblings (tripadvisor_hotels, tripadvisor_autocomplete) that could plausibly serve overlapping goals.

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.

Resources

Need Help?