TripWays

Get tour details

get_tour_details

Read-onlyIdempotent

Get the full details of one TripWays tour by bokun_id (the number in tripways.com/t/{id}): summary, itinerary stops, inclusions and exclusions, languages, cancellation policy, meeting point or pickup, from-price, rating, hero_image, url, and checkout_url. Live dates and group totals come from check_availability and get_price_quote.

Input Schema

Name	Required	Description	Default
`bokun_id`	Yes

Output Schema

Name	Required	Description
`ok`	Yes
`url`	No	The tour's TripWays page.
`error`	No	Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.
`title`	No
`rating`	No
`reason`	No	Why checkout works the way it does, e.g. pickup_required.
`themes`	No
`summary`	No
`bokun_id`	No	Tour id; the number in tripways.com/t/{id}.
`guidance`	No
`itinerary`	No
`languages`	No
`activities`	No
`exclusions`	No
`from_price`	No	What one adult pays: the tour page's From price, the same price Google shows.
`hero_image`	No	Main photo URL.
`inclusions`	No
`cancellation`	No	free, flexible, partial, or non_refundable.
`checkout_url`	No	TripWays checkout for this tour.
`destinations`	No
`hotel_pickup`	No
`duration_text`	No
`gttd_eligible`	No	Listed on Google Things to Do.
`duration_hours`	No
`bookable_natively`	No	True when checkout_url opens TripWays checkout; false when it opens the operator calendar.
`meeting_pickup_label`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / from_price / description

Previous value: -"Lowest adult price."New value: +"What one adult pays: the tour page's From price, the same price Google shows."

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / error

Added value: +{
+  "description": "Present when ok is false. code: tour_not_found, destination_not_found, destination_ambiguous, or unpriced. message is written for the traveler.",
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful context beyond them: the response is a static catalog snapshot, with live dates and group totals explicitly excluded. It doesn't mention auth requirements, rate limits, or error behavior for a nonexistent bokun_id, so it stops short of full disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key identifier and scope are front-loaded, and the second sentence is a tight hand-off to the money/availability tools. The long field enumeration partially duplicates the output schema, making one sentence do more work than necessary.

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?

An output schema exists, so return values needn't be explained, yet the description still previews the payload shape well enough to plan a call. For a single-parameter read tool with strong annotations, nothing an agent needs is missing.

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 0% for the single parameter, so the description must carry the meaning — and it does, explaining that bokun_id is the numeric id from the tripways.com/t/{id} URL. It adds no note on the digits-only pattern or what happens with an invalid id, keeping it below a 5.

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?

States a specific verb and resource ('Get the full details of one TripWays tour') and disambiguates the identifier by tying bokun_id to the number in tripways.com/t/{id}. It also enumerates the returned content and names the siblings that serve live pricing/availability, so the agent can distinguish it from check_availability without opening either 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?

Explicitly routes dynamic concerns elsewhere: 'Live dates and group totals come from check_availability and get_price_quote.' That is clear positive guidance on when to use alternatives, but it doesn't address the other overlapping siblings (get_meeting_point, get_cancellation_policy, get_tour_reviews), which return subsets of the same data.

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

All TripWays tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?