Skip to main content
Glama
chrischall

tripadvisor-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ta_get_location_details

Read-only

Retrieve complete TripAdvisor location details—names, descriptions, address, coordinates, ratings, phone, category, and URLs—using a location ID from search.

Instructions

Get full details for a TripAdvisor location: names, descriptions, address, coordinates, traveler ratings, phone, category, and listing URLs. Rating-icon and other incidental image URLs are dropped by default; pass view:"full" for TripAdvisor's whole record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.6.0
    • 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. Changed3 schema fields changedv0.1.0
    • removedInput schema / properties / currency
      Removed value: -{
-  "description": "ISO 4217 currency code for prices (default: USD)",
-  "type": "string"
-}
    • removedInput schema / properties / language
      Removed value: -{
-  "description": "Result language code (default: en)",
-  "type": "string"
-}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Preferred locales for localized fields, in priority order (e.g. [\"en\",\"es\"])",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  4. First observedv0.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral context: incidental image URLs are dropped by default, and view:"full" returns TripAdvisor's entire record. This is concrete, beyond the structured annotations, and does not contradict them.

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 purposeful sentences: the first enumerates the returned fields, the second explains the compact/full projection behavior. It is front-loaded with the core purpose and contains no filler or redundant restatement of the schema.

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?

With no output schema, the description compensates by listing the main returned field categories and clarifying the default projection behavior. The main gap is the absence of guidance for selecting this tool over sibling location tools, but overall the description is sufficient for correct invocation given the low complexity and full schema coverage.

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 description coverage is 100%, so the baseline is 3. The description adds meaning to the view parameter by giving a concrete example of what compact drops (rating-icon and incidental image URLs). It does not independently explain locale or locationId, but the schema already does that adequately.

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 names a clear verb ('get full details'), a specific resource (TripAdvisor location), and enumerates the fields returned: names, descriptions, address, coordinates, ratings, phone, category, and listing URLs. This distinguishes it from photo/review/search siblings by content, though it does not explicitly differentiate from ta_web_get_location.

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 explicit when-to-use guidance or alternatives are given. The only conditional instruction is about passing view:"full", which is a behavior choice, not a routing decision. Using this after a search is implied by the schema note on locationId, but the description itself does not say when to choose this tool over siblings.

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