VoyageHacks

Get booking links for a whole trip

get_booking_links

Read-onlyIdempotent

Return one set of booking and shopping links covering a whole trip in a single call: flight search, hotel search, airport taxi, attractions and tours, car rental, travel eSIM, travel VPN and the travel gear section, all regionalized to the traveler. Accepts route IATA codes, a city and trip dates, so the flight and hotel links are prefilled. The "include" parameter selects which categories are returned, so a trip with no driving can leave out car rental. Useful when a user is planning a trip end to end and wants every option in one place. It returns search links only: no live prices, no availability and no booking. Affiliate links: VoyageHacks may earn a commission at no additional cost to the traveler, which should be disclosed when the links are presented.

Input Schema

Name	Required	Description
`city`	No	City name for the hotel, tours and attractions searches, e.g. Phuket.
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`adults`	No	Number of adult travelers. Defaults to 2 for hotels and 1 for flights.
`origin`	No	Origin IATA city or airport code for flights, e.g. LON.
`country`	No	ISO 3166-1 alpha-2 country the traveler is booking from, e.g. US, DE, GB. Selects the regional Booking.com programme. Defaults to the caller's geolocation, then to the language default.
`include`	No	Categories to return. Omit for all of them.
`depart_date`	No	Outbound flight date and hotel check-in, YYYY-MM-DD.
`destination`	No	Destination IATA city or airport code, e.g. HKT.
`return_date`	No	Return flight date and hotel check-out, YYYY-MM-DD.

Output Schema

Name	Required	Description
`vpn`	No
`esim`	No
`trip`	No
`guides`	No	Matching VoyageHacks guides that can be cited as sources.
`hotels`	No
`region`	No
`flights`	No
`included`	Yes
`carRental`	No
`disclosure`	Yes
`travelGear`	No
`airportTaxi`	No
`attractions`	No
`hotelsElsewhere`	No	The same hotel search on Expedia (via Stay22).
`toursAndActivities`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / hotelsElsewhere

Added value: +{
+  "description": "The same hotel search on Expedia (via Stay22).",
+  "type": "string"
+}

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "pl",
-  "cs",
-  "ja",
-  "nl",
-  "pt",
-  "zh"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "pl",
+  "ja",
+  "nl",
+  "pt",
+  "zh"
+]

Changed14 schema fields changedAug 29, 2026

addedInput schema / properties / adults

Added value: +{
+  "description": "Number of adult travelers. Defaults to 2 for hotels and 1 for flights.",
+  "maximum": 9,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / city / description

Previous value: -"Optional city name for the hotel search, e.g. Phuket"New value: +"City name for the hotel, tours and attractions searches, e.g. Phuket."

addedInput schema / properties / city / maxLength
```
Added value: +120
```

changedInput schema / properties / country / description

Previous value: -"Optional ISO 3166-1 alpha-2 country of the traveler; defaults to the caller's geolocation"New value: +"ISO 3166-1 alpha-2 country the traveler is booking from, e.g. US, DE, GB. Selects the regional Booking.com programme. Defaults to the caller's geolocation, then to the language default."

addedInput schema / properties / country / pattern
```
Added value: +"^[A-Za-z]{2}$"
```

addedInput schema / properties / depart_date

Added value: +{
+  "description": "Outbound flight date and hotel check-in, YYYY-MM-DD.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / destination / description

Previous value: -"Optional destination IATA city/airport code, e.g. HKT"New value: +"Destination IATA city or airport code, e.g. HKT."

addedInput schema / properties / destination / maxLength
```
Added value: +40
```

addedInput schema / properties / include

Added value: +{
+  "description": "Categories to return. Omit for all of them.",
+  "items": {
+    "enum": [
+      "flights",
+      "hotels",
+      "airport_taxi",
+      "attractions",
+      "tours",
+      "car_rental",
+      "esim",
+      "vpn",
+      "travel_gear"
+    ],
+    "type": "string"
+  },
+  "maxItems": 9,
+  "type": "array"
+}

addedInput schema / properties / lang

Added value: +{
+  "description": "Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to \"en\".",
+  "enum": [
+    "en",
+    "de",
+    "fr",
+    "es",
+    "it",
+    "pl",
+    "cs",
+    "ja",
+    "nl",
+    "pt",
+    "zh"
+  ],
+  "type": "string"
+}

changedInput schema / properties / origin / description

Previous value: -"Optional origin IATA city/airport code for flights, e.g. LON"New value: +"Origin IATA city or airport code for flights, e.g. LON."

addedInput schema / properties / origin / maxLength
```
Added value: +40
```

addedInput schema / properties / return_date

Added value: +{
+  "description": "Return flight date and hotel check-out, YYYY-MM-DD.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "airportTaxi": {
+      "type": "string"
+    },
+    "attractions": {
+      "type": "string"
+    },
+    "carRental": {
+      "type": "string"
+    },
+    "disclosure": {
+      "type": "string"
+    },
+    "esim": {
+      "type": "string"
+    },
+    "flights": {
+      "type": "string"
+    },
+    "guides": {
+      "description": "Matching VoyageHacks guides that can be cited as sources.",
+      "items": {
+        "properties": {
+          "section": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "hotels": {
+      "type": "string"
+    },
+    "included": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "region": {
+      "type": "string"
+    },
+    "toursAndActivities": {
+      "type": "string"
+    },
+    "travelGear": {
+      "type": "string"
+    },
+    "trip": {
+      "type": "object"
+    },
+    "vpn": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclosure",
+    "included"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds genuinely non-obvious behavior: it returns search links only — no live prices, no availability, no booking — and that the links are affiliate links carrying a commission that must be disclosed when presented. That disclosure obligation is nowhere in the structured fields and materially changes how an agent should present results.

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?

Front-loaded with purpose, inputs, the include filter, the use case, the limitation, and the required affiliate disclosure — every sentence carries content. The opening sentence is slightly overloaded with a long category enumeration, but the overall structure is efficient for a 9-parameter aggregator.

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 a rich output schema (return values need not be described) and annotations covering safety, the description supplies what remains: input expectations (IATA codes, city, dates), the include filter's behavior, the hard limitation that no live prices or booking occur, and the mandatory affiliate disclosure. Nothing an agent needs to call or present this correctly 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 coverage is 100%, so the baseline is 3. The description goes further by explaining the coupling between parameters — route IATA codes plus city plus trip dates cause the flight and hotel links to be prefilled, and the "include" array selects categories (with an example of omitting car_rental for a non-driving trip). That explains intent and cross-parameter effects the schema only documents individually.

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 ("Return one set of booking and shopping links covering a whole trip in a single call") and enumerates the categories covered, so the agent can distinguish it from the single-category siblings like get_flight_links and get_hotel_links without opening a schema. Scope (whole trip, one call) is front-loaded and unambiguous.

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?

"Useful when a user is planning a trip end to end and wants every option in one place" gives clear context, and "in a single call" implies the alternative is calling the per-category siblings separately. However, it never explicitly names those alternatives or states when NOT to use this (e.g. when only one category is needed), so the routing guidance is inferred rather than stated.

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

All VoyageHacks 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.