Skip to main content
Glama
chrischall

viator-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vt_search_freetext

Read-only

Search Viator tours, attractions, and destinations by free text, such as 'colosseum underground tour', to quickly find options without needing a destination ID.

Instructions

Free-text search across Viator products, attractions, and destinations (e.g. "colosseum underground tour"). The fastest way to find things when you don't have a destination id yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoProduct sort key
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact (default) projects the PRODUCT results down to their product code, title, from-price and currency, rating, review count, duration, confirmation type, flags, booking URL and cover image and strips image/avatar URLs from the attraction and destination results; "full" returns Viator's payload untouched.
countNoResults per page per type (max 50; default 10)
orderNoSort direction
startNo1-based index of the first result (per type)
currencyNoCurrency for request/response prices (default USD)USD
end_dateNoOnly products operating on/before this date (YYYY-MM-DD)
max_priceNoMaximum product from-price (in currency)
min_priceNoMinimum product from-price (in currency)
min_ratingNoMinimum average traveler rating (0-5)
start_dateNoOnly products operating on/after this date (YYYY-MM-DD)
destinationNoRestrict product results to a destination id
search_termYesFree-text search term
search_typesNoWhich result types to return (default: PRODUCTS only)
campaign_valueNoAffiliate campaign tracking id — appended to the productUrl/attractionUrl/destinationUrl Viator returns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.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 changedv1.2.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "default": false,
-  "description": "Return slim product summaries 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 (default) projects the PRODUCT results down to their product code, title, from-price and currency, rating, review count, duration, confirmation type, flags, booking URL and cover image and strips image/avatar URLs from the attraction and destination results; \"full\" returns Viator's payload untouched.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv1.0.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to cover the safety profile. The description adds the cross-type search scope but makes a performance claim ('fastest way') without qualification. It doesn't disclose return format or pagination, but given annotations carry the safety burden, this is adequate.

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 with zero waste. The search scope and example are front-loaded, and the usage guidance ('when you don't have a destination id yet') is placed second. Every word 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?

The description covers purpose, scope, and usage context, and the schema fully documents parameters. The main gap is result structure since there's no output schema, but the 'view' parameter partially documents response shape. Adequate for the tool's primary use case.

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 15 parameters are documented in the input schema. The description itself adds no parameter-level detail, relying on the schema, which is the appropriate baseline. No extra value beyond schema coverage, but none is needed.

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 (search), resource (Viator products, attractions, destinations), and gives a concrete example ('colosseum underground tour'). It clearly distinguishes from siblings like vt_search_products and vt_search_attractions by emphasizing the free-text, cross-type scope.

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?

Explicitly states the usage condition: 'the fastest way to find things when you don't have a destination id yet.' This tells the agent when to choose it over destination-scoped searches. However, it doesn't name alternatives explicitly or state exclusions (e.g., when to use vt_search_products instead).

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