Skip to main content
Glama
chrischall

tripadvisor-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ta_get_location_reviews

Read-only

Fetch traveler reviews for a TripAdvisor location using its location ID, with pagination and locale preferences. Choose compact or full view to control response detail.

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.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 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"
+}
  3. 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"
+}
  4. First observedv0.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool read-only, and the description adds real behavioral detail: pagination support and the default stripping of reviewer avatars/image URLs, plus the view:'full' opt-in. It does not discuss rate limits or response envelopes, but that is less critical given the readOnlyHint.

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 deliver the purpose, pagination, and the non-obvious default behavior up front. Every clause earns its place with no filler.

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 read-only paginated listing with a fully documented schema and clear annotations, the description is sufficient. An agent knows what it retrieves, how to paginate, and how to opt into full records without needing further context.

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 all five parameters are already documented with types, constraints, and enum meanings. The description's view commentary mirrors the schema's view description rather than adding new parameter meaning.

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 operation ('Get traveler reviews'), the resource ('a TripAdvisor location'), and a key capability (pagination). This clearly distinguishes it from related siblings like ta_get_location_photos and ta_get_location_details.

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 phrasing makes the intended use obvious: retrieve reviews for a location. It does not explicitly name alternatives or exclusion cases, but siblings are semantically distinct enough that an agent is unlikely to confuse this with photo or location-detail tools.

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

Deploy Server

Other Tools