Skip to main content
Glama
chrischall

tripadvisor-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ta_get_location_photos

Read-only

Get photos for a TripAdvisor location by ID, including pagination, multi-size image URLs, source, and dimensions.

Instructions

Get photos for a TripAdvisor location (multi-size image URLs, source, dimensions), with pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage index (1-based)
sizeNoResults per page (max 20)
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. Changed7 schema fields changedv0.1.0
    • removedInput schema / properties / language
      Removed value: -{
-  "description": "Caption language code (default: en)",
-  "type": "string"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Number of photos 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 photo",
-  "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"
+}
    • removedInput schema / properties / source
      Removed value: -{
-  "description": "Comma-separated photo sources to allow: Expert, Management, Traveler (default: all)",
-  "pattern": "^(Expert|Management|Traveler)(,(Expert|Management|Traveler))*$",
-  "type": "string"
-}
  3. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate a read-only, open-world operation. The description adds useful behavioral context: results are paginated and include specific image-related fields. It does not explain pagination termination semantics, but given the annotation coverage this is acceptable.

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?

A single sentence that front-loads the action and resource, then packs the return details and pagination into a parenthetical. Every phrase earns its place; no filler or redundancy.

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

Completeness3/5

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

The description gives the key return fields and mentions pagination, and the schema fully documents parameters. However, with no output schema, an agent is not told how to detect the last page or what the response envelope looks like, leaving a minor but real gap.

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 the schema already documents all four parameters. The description only generically references pagination, adding no meaningful parameter semantics beyond what the schema provides.

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 names a specific action ('Get photos') and a specific resource ('TripAdvisor location'), then lists the meaningful payload characteristics (multi-size image URLs, source, dimensions). It is clearly distinct from sibling tools like reviews, details, and search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is inferable: call this when you need photos for a TripAdvisor location. However, it does not explicitly state when not to use it or mention alternatives like ta_get_location_details or ta_get_location_reviews.

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