Outscraper MCP

Official

Overview Schema Source Related Servers Discussions Admin

Tripadvisor Reviews

tripadvisor_reviews

Fetch Tripadvisor reviews from any URL via Outscraper's dedicated endpoint. Set review limits, language, and async mode to collect structured review data for analysis.

Instructions

Fetch Tripadvisor reviews with the documented /tripadvisor-reviews endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`async`	No	Deprecated compatibility flag. Prefer execution_mode.
`query`	Yes	One or more Tripadvisor URLs.
`cutoff`	No	Cutoff value accepted by Outscraper.
`fields`	No	Specific fields to return.
`webhook`	No	Optional webhook URL for async completion.
`language`	No	Language code.
`reviews_limit`	No	Maximum reviews per query.
`execution_mode`	No	Execution strategy. Use auto to let the MCP server choose between sync and async.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`async`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.5Sep 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.2.3Aug 1, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'fetch,' without mentioning how the endpoint behaves regarding async execution, webhooks, cutoff handling, or response structure. This is minimal but not misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but part of it is filler: 'with the documented /tripadvisor-reviews endpoint' adds little since the endpoint is implied by the tool name. It is concise but misses an opportunity to convey meaningful guidance.

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?

Despite having an output schema and well-documented parameters, this 8-parameter tool still needs usage context that the description does not provide. There is no indication of how to construct queries, what the output represents, or how async/webhook behavior should be handled.

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 parameters are already documented with descriptions like 'One or more Tripadvisor URLs' and 'Execution strategy.' The tool description adds no extra semantic value beyond what the schema provides, so the baseline 3 is appropriate.

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 verb and resource: 'Fetch Tripadvisor reviews.' This distinguishes it from broad search tools like tripadvisor_search, though it does not explicitly differentiate it from other review-focused siblings such as booking_reviews or yelp_reviews.

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 given on when to choose this tool over alternatives. The description does not explain that Tripadvisor URLs are required, when async execution makes sense, or when to use another scraper or review tool.

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