Skip to main content
Glama
chrischall

tripadvisor-mcp

by chrischall
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ta_get_location_reviews

Read-only

Fetch traveler reviews for any TripAdvisor location with pagination controls. Choose compact or full records to get review details, localized where available.

Instructions

Get traveler reviews for a TripAdvisor location, with pagination. Reviewer avatars and other image URLs are dropped by default; pass view:"full" for TripAdvisor's whole records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage index (1-based)
sizeNoResults per page (max 20)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; "full" returns TripAdvisor's whole records.
localeNoPreferred locales for localized fields, in priority order (e.g. ["en","es"])
locationIdYesTripAdvisor location ID (from a search tool)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact returns the slim projection where one exists and strips image URLs elsewhere; \"full\" returns TripAdvisor's whole records.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed6 schema fields changedv0.1.0
    • removedInput schema / properties / language
      Removed value: -{
-  "description": "Review language code (default: en)",
-  "type": "string"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Number of reviews to return",
-  "exclusiveMinimum": 0,
-  "maximum": 9007199254740991,
-  "type": "integer"
-}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Preferred locales for localized fields, in priority order (e.g. [\"en\",\"es\"])",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Index of the first review",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page index (1-based)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Results per page (max 20)",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}
  3. First observedv0.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already signal a safe, externally-sourced read operation. The description adds useful behavioral detail beyond those annotations: avatars and image URLs are dropped by default, and passing view:"full" returns TripAdvisor's whole records. This helps the agent predict response differences.

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 sentences, no filler. The core purpose and pagination are front-loaded, and the important default-vs-full behavior is explained immediately after. Every sentence earns its place.

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?

For a read-only paginated listing tool, the description covers the essential invocation context: resource, pagination, and response-shape behavior. The schema handles parameter details. It does not describe the output shape, but no output schema exists and the tool's read-only nature lowers the risk of misinterpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description adds practical meaning by explaining the default effect of the view parameter and the pagination capability, which helps an agent choose the right values without diving into schema nuances.

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?

The description states a specific verb and resource: get traveler reviews for a TripAdvisor location. Saying "traveler reviews" cleanly distinguishes this from the sibling tools for search, details, photos, and general location lookup.

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 description makes the context clear: use this tool when traveler reviews for a location are needed. It does not explicitly name alternatives or exclusions, but the sibling names and the singular review focus provide enough directional guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/tripadvisor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server