Crawlora MCP

tripadvisor_reviews

Read-only

Fetch normalized public review items for a TripAdvisor place using its ID or URL. Use tripadvisor_search to find a place or tripadvisor_place for its profile and location details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tripadvisor_reviews"
  }
}

Input Schema

Name	Required	Description
`id`	No	TripAdvisor location id; provide either id or url.
`url`	No	TripAdvisor place URL; provide either id or url.
`page`	No	Result page, default 1.
`limit`	No	Max number of reviews to return per page.
`ratings`	No	Optional repeated star-rating filters; each value from 1 to 5.
`sort_by`	No	Sort order. Allowed values: FAVORABLE_RATING, DATE. Default FAVORABLE_RATING.
`language`	No	Review language code, e.g. en, fr, zh-CN.
`sort_type`	No	Sort type. Allowed values: ML_SORTED, DEFAULT. Default ML_SORTED.
`do_machine_translation`	No	When true, include machine-translated review text.
`photos_per_review_limit`	No	Max number of photos to include per review.

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.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / ratings / items / description
```
Added value: +"Documented values: 1, 2, 3, 4, 5."
```
First observedOct 5, 2026

TDQS

A4/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 useful scoping context ('normalized public review items', requires id or url) but says nothing about pagination behavior, rate limits, or how large result sets are handled, so it adds only moderate value over the annotations.

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?

Two tight sentences, zero waste. The core action is front-loaded and the sibling-routing guidance follows immediately, which is exactly what an agent needs in order of priority.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and annotations cover the safety profile; the description correctly focuses on purpose and routing. The only minor gap is that pagination/filter behavior isn't hinted at, but the fully documented schema compensates.

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% across all 10 parameters – filters (ratings, language), sorting (sort_by, sort_type), pagination (page, limit), translation, and photo limits are all documented in the schema. The description only echoes the id/url requirement, so baseline 3 is appropriate; it adds essentially nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Fetch normalized public review items') scoped to a TripAdvisor place, and explicitly separates itself from siblings by naming tripadvisor_search (place lookup) and tripadvisor_place (profile/location details). An agent can distinguish this from the other tripadvisor_* tools without opening any schema.

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?

The second sentence routes the agent to the right sibling depending on what it needs (search to find a place, place for profile/location). It implies this tool is for review retrieval and that an id or url is required, but does not spell out the when-not condition (e.g., that it returns only reviews, not ratings summaries) as explicitly.

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?