tripadvisor-mcp

ta_search_nearby

Read-only

Find TripAdvisor locations near a point using latitude/longitude, a reference location ID, or bounding box with radius. Returns matches with distance and location IDs for hotels, restaurants, and attractions.

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

Name	Required	Description
`lat`	No	Center latitude (with lon+radius)
`lon`	No	Center longitude (with lat+radius)
`page`	No	Page index (1-based)
`size`	No	Results per page (max 20)
`sort`	No	Sort order (default distance)
`unit`	No	Radius unit (default MI)
`view`	No	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.
`locale`	No	Preferred locales for localized fields, in priority order (e.g. ["en","es"])
`ne_lat`	No	Bounding box NE latitude
`ne_lon`	No	Bounding box NE longitude
`radius`	No	Search radius (required with lat/lon or location_id; must be > 0)
`sw_lat`	No	Bounding box SW latitude
`sw_lon`	No	Bounding box SW longitude
`category`	No	Restrict to one category
`min_rating`	No	Minimum traveler rating (1.0–5.0)
`location_id`	No	Reference location as center (with radius)
`include_photo`	No	Include a photo per result

Schema Changelog

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

Changed2 schema fields changedv0.5.1Sep 5, 2026

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"
+}

Changed10 schema fields changedv0.3.0Jul 14, 2026

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"
-]

Changed18 schema fields changedv0.1.0Jul 5, 2026

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"
+]

First observedv0.0.0Jul 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral detail beyond that: it states that results include distance and a location id, and that slim summaries are returned by default while view:'full' returns whole records. This helps the agent understand response shape expectations.

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?

The description is only two sentences, front-loads the core purpose, and every clause adds information: the spatial modes, the response fields, and the view switch. There is no filler or repetition of schema details.

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?

Given the high parameter count, 100% schema coverage, and no output schema, the description is adequately complete: it explains the essential invocation modes and the output shape. It could go slightly further by explicitly stating that the three center modes are mutually exclusive, but the word 'or' conveys that reasonably well.

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 schema already documents each parameter. The description adds semantic grouping by explaining that lat+lon, location_id, and sw/ne bbox each serve as different center/region modes, and clarifies the meaning of the default versus full view. This exceeds the baseline for high schema coverage.

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 opens with a specific verb and resource: 'Find TripAdvisor locations near a point within a radius, or inside a bounding box.' It clearly differentiates this tool from siblings like ta_search_locations and ta_get_locations by emphasizing geospatial proximity search, so an agent can tell what this tool is for without opening the schema.

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 provides clear usage context by enumerating the three supported center modes: lat+lon+radius, location_id+radius, and sw/ne bounding box. It does not explicitly name alternative sibling tools or tell the agent when not to use this tool, but the mode guidance is concrete and actionable.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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