Skip to main content
Glama

MolTravel

by com.moltravel

tourradar_vertex-review-search

[tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoShort natural language search query to find specific review topics. Keep it concise — do NOT expand into keyword lists. Use simple phrases like 'food quality', 'guide', 'hotel issues'. The search engine handles semantic matching automatically. Prefer using 'keywords' parameter instead when user intent maps to specific topics. Leave empty to return all reviews.
tourIdsNoTour IDs to scope reviews to specific tours. Use vertex-tour-title-search to find tour IDs if needed.
keywordsNoArray of keyword phrases to search reviews for. These are joined with OR logic to find reviews matching any of the given topics. Use short phrases (e.g., ['food quality', 'meals', 'restaurant']). When provided, this takes priority over 'query'.
pageSizeNoNumber of reviews to return (1-20, default 10)
minRatingNoOnly return reviews with a star rating >= this value (1-5). Use to surface only strong reviews.
pageTokenNoToken for fetching the next page of results. Use the nextPageToken value from a previous response.
createdAfterNoOnly return reviews created on or after this date (YYYY-MM-DD). Use to bias toward recent reviews.
travelledAfterNoOnly return reviews whose trip departed on or after this date (YYYY-MM-DD). Use to surface reviews from recent travellers.

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses key behaviors: AI-powered semantic search, the requirement for tourIds, and the optional text query for topic filtering. It doesn't mention output format or pagination behavior, but for a read-only search tool this is adequate context. The note about combining with a query adds useful behavioral detail beyond structured fields.

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 compact and front-loaded. The first sentence states the core purpose. Each subsequent sentence adds essential context: requirement, when to use, how to combine query, and fallback to sibling tools. No filler or repetition — 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 an 8-parameter tool with no output schema, the description provides sufficient context: purpose, required scope, usage timing, and alternatives. It doesn't cover pagination or default sorting, but the schema fully documents parameters. The tool description is complete enough for an agent to select and invoke it correctly.

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 extra value by explaining that the query should be 'short natural language', providing concrete examples ('food', 'guide', 'accommodation'), and explicitly recommending the 'keywords' parameter when topics are known. This reinforces and clarifies the schema without being redundant.

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: 'Search tour reviews using AI-powered semantic search.' It specifies the resource (tour reviews), the action (search), and the key constraint (requires tourIds to scope results). This distinguishes it from sibling tools like vertex-tour-search and vertex-tour-title-search, which are explicitly named as alternatives for finding tours first.

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?

The description provides explicit when-to-use guidance: 'Use this when the user asks about reviews, feedback, or experiences for specific tours.' It also gives clear alternatives: 'When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.' This is strong, actionable usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MolTravel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

Most tools are namespaced by vendor and resource, so ferry, tour, flight, hotel, and experience searches are broadly distinguishable. However, hotel search exists in both skiplagged and trivago, ferryhopper_search_trips is a deprecated duplicate of search_trips_v2, and several skiplagged calendar/anywhere tools overlap in flight-price discovery, which can cause misselection.

Naming Consistency2/5

Naming conventions are mixed across the set: plain underscores (airports_search), vendor-prefixed underscores (ferryhopper_get_ports), redundant prefixes (skiplagged_sk_hotels_search, trivago_trivago-accommodation-search), and hyphenated sub-APIs (tourradar_b2b-tour-details, tourradar_vertex-tour-search). There is no consistent verb_noun pattern and at least one version-suffixed deprecated name.

Tool Count1/5

With 56 tools, the server falls into the extreme-mismatch count band. The breadth is partly explained by eight vendor integrations, but many lookups, near-duplicate searches, and deprecated tools could be consolidated or split into focused MCP servers.

Completeness4/5

The tool surface covers most of the travel-planning lifecycle: airports, airlines, visa rules, FCDO advice, flights, hotels, cars, ferries, experiences, and tours including search, details, and tour booking. The main gaps are that only tours have an actual booking flow and there is no update/cancel or post-booking management.

Resources