Skip to main content
Glama
chrischall

tripadvisor-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ta_search_nearby

Read-only

Find nearby TripAdvisor hotels, restaurants, or attractions by coordinates, reference location, or bounding box. Returns matches with distance and location ID, with compact or full details.

Instructions

Find TripAdvisor locations near a point within a radius, or inside a bounding box. Center by lat+lon+radius, by a reference location_id+radius, or by a sw/ne bounding box. Returns matches with distance and a location id. Returns slim summaries by default; pass view:"full" for the whole records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoCenter latitude (with lon+radius)
lonNoCenter longitude (with lat+radius)
pageNoPage index (1-based)
sizeNoResults per page (max 20)
sortNoSort order (default distance)
unitNoRadius unit (default MI)
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"])
ne_latNoBounding box NE latitude
ne_lonNoBounding box NE longitude
radiusNoSearch radius (required with lat/lon or location_id; must be > 0)
sw_latNoBounding box SW latitude
sw_lonNoBounding box SW longitude
categoryNoRestrict to one category
min_ratingNoMinimum traveler rating (1.0–5.0)
location_idNoReference location as center (with radius)
include_photoNoInclude a photo per result

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. Changed2 schema fields changedv0.5.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return a slim summary per result (id, name, category, city, rating, review_count, url) instead of full records",
-  "type": "boolean"
-}
    • 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. Changed10 schema fields changedv0.3.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Return a slim summary per result (id, name, category, city, rating, review_count, url) instead of full records",
+  "type": "boolean"
+}
    • changedInput schema / properties / lat / description
      Previous value: -"Center latitude"New value: +"Center latitude (with lon+radius)"
    • addedInput schema / properties / location_id
      Added value: +{
+  "description": "Reference location as center (with radius)",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / properties / lon / description
      Previous value: -"Center longitude"New value: +"Center longitude (with lat+radius)"
    • addedInput schema / properties / ne_lat
      Added value: +{
+  "description": "Bounding box NE latitude",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}
    • addedInput schema / properties / ne_lon
      Added value: +{
+  "description": "Bounding box NE longitude",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius (must be > 0)"New value: +"Search radius (required with lat/lon or location_id; must be > 0)"
    • addedInput schema / properties / sw_lat
      Added value: +{
+  "description": "Bounding box SW latitude",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}
    • addedInput schema / properties / sw_lon
      Added value: +{
+  "description": "Bounding box SW longitude",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}
    • removedInput schema / required
      Removed value: -[
-  "lat",
-  "lon",
-  "radius"
-]
  4. Changed18 schema fields changedv0.1.0
    • removedInput schema / properties / address
      Removed value: -{
-  "description": "Address filter",
-  "type": "string"
-}
    • changedInput schema / properties / category / description
      Previous value: -"Restrict results to one property type"New value: +"Restrict to one category"
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "hotels",
-  "attractions",
-  "restaurants",
-  "geos"
-]New value: +[
+  "RESTAURANT",
+  "ATTRACTION",
+  "HOTEL"
+]
    • addedInput schema / properties / include_photo
      Added value: +{
+  "description": "Include a photo per result",
+  "type": "boolean"
+}
    • removedInput schema / properties / language
      Removed value: -{
-  "description": "Result language code (default: en)",
-  "type": "string"
-}
    • addedInput schema / properties / lat
      Added value: +{
+  "description": "Center latitude",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}
    • removedInput schema / properties / latLong
      Removed value: -{
-  "description": "Center point, e.g. \"42.3455,-71.10767\"",
-  "pattern": "^-?\\d+(\\.\\d+)?\\s*,\\s*-?\\d+(\\.\\d+)?$",
-  "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"
+}
    • addedInput schema / properties / lon
      Added value: +{
+  "description": "Center longitude",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}
    • addedInput schema / properties / min_rating
      Added value: +{
+  "description": "Minimum traveler rating (1.0–5.0)",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page index (1-based)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / phone
      Removed value: -{
-  "description": "Phone number filter (spaces/dashes ok, no leading \"+\")",
-  "type": "string"
-}
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius around latLong (must be > 0)"New value: +"Search radius (must be > 0)"
    • removedInput schema / properties / radiusUnit
      Removed value: -{
-  "description": "Unit for radius",
-  "enum": [
-    "km",
-    "mi",
-    "m"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Results per page (max 20)",
+  "maximum": 20,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Sort order (default distance)",
+  "enum": [
+    "distance",
+    "rating"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / unit
      Added value: +{
+  "description": "Radius unit (default MI)",
+  "enum": [
+    "MI",
+    "KM"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "latLong"
-]New value: +[
+  "lat",
+  "lon",
+  "radius"
+]
  5. First observedv0.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already convey read-only and open-world behavior, so the bar is lower. The description adds value by disclosing that slim summaries are the default and that view='full' returns whole records, plus that results carry distance and location id. It does not cover pagination or errors, but those are not critical given the annotations.

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?

Three sentences, each carrying distinct information: purpose, parameter modes, and return shape. No filler or repetition; the structure front-loads the core action before the detailed modes.

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 17-parameter tool with no output schema, the description covers the essential conditional groups and response-shape options. It does not explicitly state that exactly one mode must be chosen or define pagination defaults, but the schema covers defaults and the mode phrasing implies alternatives. Overall it is sufficient for correct invocation.

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 baseline is 3. The description adds real semantic value by grouping parameters into three accepted modes ('Center by lat+lon+radius, by a reference location_id+radius, or by a sw/ne bounding box') and clarifying the 'view' parameter's default behavior, which is above the baseline.

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: 'Find TripAdvisor locations near a point within a radius, or inside a bounding box.' This clearly distinguishes it from sibling search tools like ta_search_locations by emphasizing geospatial proximity and box searches.

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?

It explains three invocation modes (lat/lon+radius, location_id+radius, bounding box), giving clear context on how to parameterize the call. However, it does not explicitly state when to prefer this tool over ta_search_locations or mention exclusions, so usage guidance is implied rather than explicit.

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