tripadvisor-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.5.1
Disambiguation4/5
Search and retrieval tools are mostly distinct, but ta_get_locations and ta_get_location_details overlap in purpose (batch vs single details) and ta_web_get_location duplicates ta_get_location_details as a fallback. Descriptions cross-reference these relationships clearly, so an agent can generally select correctly after reading them.
Naming Consistency4/5
All names share a ta_ prefix and snake_case, and most use search_/get_ verbs followed by a resource. The deviations are ta_web_healthcheck (noun rather than verb) and ta_web_get_location's web_ prefix, but these are minor and predictable.
Tool Count5/5
Eight tools is a well-scoped set for a TripAdvisor read-only data server: two search modes, four location-data/resource getters, and two web-bridge utilities. None feel redundant enough to cut, and the count is comfortably in the ideal 3–15 range.
Completeness4/5
The core domain—location search, nearby discovery, batch lookup, full details, photos, and reviews—is covered, and the web fallback plus healthcheck address access failures. The only minor gap is that the web fallback doesn't extend to photos/reviews, so an API outage would still block those workflows.
Average 4.3/5 across 8 of 8 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- 11 of 11 community issues answered or closed in the last 6 months
- 78 commits in the last 12 weeks
- Last stable release on September 5, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint and openWorldHint. Description adds that it returns 'full details' with specific fields, but does not elaborate on behavioral traits like idempotency, rate limits, or what happens if locationId is invalid. No contradiction with 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?
Single sentence that front-loads the purpose and enumerates key returned data without unnecessary words. Efficient and well-structured.
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 tool's simplicity and full parameter coverage, the description is complete enough. It lists major return fields, though output schema is absent. Works well with annotations.
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 coverage is 100%, with descriptions for locationId and locale. The description repeats some parameter context by listing returned fields, but does not add new meaning 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 specifies the action 'Get full details' for a TripAdvisor location, lists specific fields (names, descriptions, address, coordinates, traveler ratings, phone, category, listing URLs), and distinguishes it from sibling tools like ta_get_location_photos or ta_get_location_reviews.
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?
No explicit guidance on when to use this tool vs siblings (e.g., after search to get full details). The description implies it retrieves details for a known locationId, but does not state alternatives or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the bar is lower. The description adds useful behavioral context beyond those annotations: results are slim by default, pagination is included, and view:"full" returns complete records. This is meaningful for an agent deciding whether the default response is sufficient.
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 with no filler: the action and scope come first, followed by the output contract and the key view modifier. Every sentence earns its place.
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 search tool with no output schema, the description sufficiently conveys what the agent can expect: location ids, pagination, and slim-vs-full response shapes. The remaining parameter details are fully covered by the input schema, though the description could have briefly mentioned scoping filters like geo_name or postal_code.
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 value by mapping the categories to "restaurants, attractions, hotels" and clarifying the effect of the view parameter between slim and full records, which complements the schema's enum descriptions.
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 clearly states a specific action (search TripAdvisor locations by name) and resource type (restaurants, attractions, hotels). It also explains the key output (location ids for detail tools) and pagination, which helps position it against the get_* and search_nearby siblings, though it does not explicitly name a sibling.
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 the intended workflow: search by name, then use the returned location id with the detail tools. It does not explicitly state when to prefer ta_search_nearby or ta_get_locations instead, nor does it mention exclusions such as searching by coordinates.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond annotations by specifying the output (URLs, source, dimensions) and pagination support. Annotations already indicate readOnlyHint and openWorldHint, and the description aligns with those without contradiction.
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 a single sentence that efficiently conveys the purpose and key return data. It is front-loaded and contains no unnecessary words.
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 simple read-only tool with good annotations and a self-documenting schema, the description provides sufficient context about output and pagination. It could be improved by noting the necessity of locationId from a search, but schema already covers that.
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% (all 4 parameters have descriptions). The tool description does not add additional meaning beyond what is already in the schema; it only mentions pagination which is implied by page and size parameters.
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 action 'Get photos' and the resource 'TripAdvisor location', and specifies the returned data: 'multi-size image URLs, source, dimensions'. It also mentions pagination, which distinguishes it from sibling tools like ta_get_location_details or ta_get_location_reviews.
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 retrieving photos, but does not explicitly state when to use versus alternatives or any exclusions. Sibling tool names provide context, but no direct guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already signal a safe, externally-sourced read operation. The description adds useful behavioral detail beyond those annotations: avatars and image URLs are dropped by default, and passing view:"full" returns TripAdvisor's whole records. This helps the agent predict response differences.
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 sentences, no filler. The core purpose and pagination are front-loaded, and the important default-vs-full behavior is explained immediately after. Every sentence earns its place.
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 paginated listing tool, the description covers the essential invocation context: resource, pagination, and response-shape behavior. The schema handles parameter details. It does not describe the output shape, but no output schema exists and the tool's read-only nature lowers the risk of misinterpretation.
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 schema already documents all parameters. The description adds practical meaning by explaining the default effect of the view parameter and the pagination capability, which helps an agent choose the right values without diving into schema nuances.
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: get traveler reviews for a TripAdvisor location. Saying "traveler reviews" cleanly distinguishes this from the sibling tools for search, details, photos, and general location lookup.
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 makes the context clear: use this tool when traveler reviews for a location are needed. It does not explicitly name alternatives or exclusions, but the sibling names and the singular review focus provide enough directional guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful behavioral context beyond the readOnlyHint and openWorldHint annotations: it discloses that unknown or unlicensed ids are silently omitted, which is critical for interpreting sparse results. It also notes default vs. full response shapes, though the schema already details this. This is helpful behavior disclosure without contradicting 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?
The description is two compact sentences that front-load the core purpose and the key behavioral caveat. Every sentence adds value: purpose, cost comparison, silent omission, and view behavior. No filler or redundant restatement of the tool name.
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 does enough to set expectations for the response (slim summaries vs. full records) and covers the main edge case (silently omitted ids). Locale parameter is left to the schema, which is acceptable. It is complete enough for an agent to decide when and how to invoke, though a bit more detail on the response structure would push it to 5.
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 coverage is 100%, so the schema already documents all three parameters. The description mostly echoes what the schema states (array of ids, full view option) rather than adding new parameter-level meaning. Baseline 3 is appropriate; no additional semantics are introduced in the description.
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 gets details for multiple locations in one batch call, contrasting it with the single-location sibling ta_get_location_details. The verb 'Get' plus resource 'locations' and the MULTIPLE/batch qualifier leave no ambiguity about what this tool does and how it differs from its siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly positions the tool as the cheaper alternative to repeated ta_get_location_details calls, giving a clear 'when to use' condition. The note about unknown or unlicensed ids being silently omitted also helps the agent set expectations before invoking and advises against using this when missing ids matter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral context: it makes an external network round-trip, requires no auth, returns specific diagnostic fields, and distinguishes failure categories such as 'bridge never came up' versus 'extension not connected.'
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 dense but every phrase earns its place: the action, exact test target, returned diagnostics, failure categories, usage trigger, and auth requirements are all packed in without redundancy. The key verb and purpose are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no parameters, the description carries the full burden of explaining behavior, return values, and usage. It does so thoroughly by enumerating the diagnostics, the failure modes it disambiguates, and the precise condition under which to call it.
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?
The tool has zero parameters, so there is no parameter documentation burden. The schema is empty and fully covered, and the description clarifies that the tool performs a fixed diagnostic action without requiring inputs.
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 — round-tripping a small public Tripadvisor URL through the fetchproxy bridge — and clearly identifies the output as diagnostics. It distinguishes this from the sibling data-fetching tools by framing it as a health check for the bridge rather than a content lookup.
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?
It explicitly states when to call: 'Call this when a real tool fails and you want to know which hop broke.' This gives a clear diagnostic trigger context, though it does not spell out when not to use it or name alternative diagnostic tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses behavioral traits beyond annotations: reads from public page via browser bridge, works without API key, does not return individual review text. Annotations already declare readOnlyHint and openWorldHint, and description adds useful 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?
Three sentences, front-loaded with the main action, no unnecessary words. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 parameter, no output schema), the description adequately lists return fields, covers supported location types, and notes what it does not return. Complete for agent decision-making.
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% for the single parameter locationId, and the description repeats the same description from the schema without adding new semantic meaning. Baseline 3 is appropriate.
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 gets core TripAdvisor location details by ID, listing specific fields, and distinguishes from sibling ta_get_location_details by noting it uses browser bridge and works without API key.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to use this tool when ta_get_location_details is unavailable or its key is blocked, providing clear context for when to use vs alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![tripadvisor-mcp MCP server](https://glama.ai/mcp/servers/chrischall/tripadvisor-mcp/badges/card.svg)](https://glama.ai/mcp/servers/chrischall/tripadvisor-mcp)

Score Badge

Copy to your README.md:

[![tripadvisor-mcp MCP server](https://glama.ai/mcp/servers/chrischall/tripadvisor-mcp/badges/score.svg)](https://glama.ai/mcp/servers/chrischall/tripadvisor-mcp)

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