Skip to main content
Glama

ta_search_nearby

Read-only

Find TripAdvisor attractions, restaurants, and hotels near a point or within a bounding box, with radius search and compact summaries.

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. Pass compact:true for slim summaries.

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)
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
compactNoReturn a slim summary per result (id, name, category, city, rating, review_count, url) instead of full records
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
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and result variability. The description adds the compact mode option but does not disclose other behavioral traits like rate limits, authentication needs, or pagination behavior. With annotations doing most of the heavy lifting, the description contributes modest additional context.

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 concise (three sentences) and front-loaded with the core purpose. Every sentence adds meaningful information without redundancy.

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 read-only spatial search tool with good annotations and full schema coverage, the description covers key search modes and output (distance, location id). However, it omits mention of pagination (page/size parameters) which is a minor gap given the tool's complexity.

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 individual parameter details are documented. The description adds value by grouping parameters into three search modes (lat+lon+radius, location_id+radius, bounding box) and explaining the compact flag, which helps the agent understand parameter combinations beyond the schema.

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 clearly states the tool's purpose: 'Find TripAdvisor locations near a point within a radius, or inside a bounding box.' It specifies the three search methods (lat+lon+radius, location_id+radius, bounding box) and what is returned (matches with distance and location id), effectively distinguishing it from sibling tools like ta_search_locations.

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 description implies usage for proximity search but does not provide explicit when-to-use or when-not-to-use guidance compared to sibling tools. No alternatives or exclusions are mentioned, leaving the agent to infer context from tool names.

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

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