tripadvisor_search
Search TripAdvisor places. Returns normalized TripAdvisor place listings for hotels, restaurants, attractions, and supported attraction category types.
This record as markdown: /tools/crawlora-mcp/tripadvisor-search.md
What tripadvisor_search does on Crawlora
AI agents call tripadvisor_search to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | Sort value |
type | string | Yes | Listing type |
class | integer | — | Hotel class filter |
limit | integer | — | Maximum results |
geo_id | integer | Yes | TripAdvisor geo id |
locale | string | — | TripAdvisor locale |
offset | integer | — | Zero-based result offset |
currency | string | — | Currency code |
amenities | array | — | Hotel amenity filter ids |
filter_id | string | — | Optional hotel filter id |
price_max | integer | — | Maximum hotel price filter |
price_min | integer | — | Minimum hotel price filter |
Parameters from the server's own tool schema.
Why tripadvisor_search is rated Low
This tool performs a search query against TripAdvisor's public data, returning listings of hotels, restaurants, and attractions. It retrieves information without creating, modifying, deleting, or executing any operations. No side effects occur beyond data fetching.
From the tool's definition Tool description states it 'Search[es] TripAdvisor places' and 'Returns normalized TripAdvisor place listings' — a retrieval operation with no modification or execution of external actions.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs tripadvisor_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tripadvisor_search, this is the rule to start with:
tripadvisor_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every tripadvisor_search call is checked against it from then on.
Questions about tripadvisor_search
Search TripAdvisor places. Returns normalized TripAdvisor place listings for hotels, restaurants, attractions, and supported attraction category types. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
tripadvisor_search accepts 12 parameters: sort, type, class, limit, geo_id, locale, offset, currency, amenities, filter_id, price_max, price_min. Required: type, geo_id. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for tripadvisor_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crawlora. Nothing to install.
tripadvisor_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tripadvisor_search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for tripadvisor_search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
tripadvisor_search is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue