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. Each per-topic tool (get_flight_links, get_hotel_links, get_esim_links and the rest) returns richer detail and more guides for a single category. 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

TableJSON 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

TableJSON 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
`toursAndActivities`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.9/5.0

Behavior5/5

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

Beyond the readOnlyHint, idempotentHint, and destructiveHint annotations, the description discloses meaningful behavioral facts: it 'returns search links only: no live prices, no availability and no booking', notes affiliate commission and disclosure obligations, and explains that results are regionalized and prefilled. These are material behaviors an agent cannot infer from the schema or annotations alone.

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 front-loaded with the core purpose and scope, then moves to usage guidance, limitations, and the affiliate disclosure. Every sentence carries distinct information, and 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity — 9 optional parameters, an output schema, and a large sibling set — the description covers purpose, scope, selection criteria, alternatives, limitations, and even a compliance note about affiliate links. An agent has enough context to decide whether to invoke it and what to expect from the result.

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 baseline is 3. The description adds value by explaining that route IATA codes, a city, and trip dates cause flight and hotel links to be prefilled, and that the 'include' parameter selects which categories are returned, with the car-rental example reinforcing optionality. This goes beyond simply restating parameter names.

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: 'Return one set of booking and shopping links covering a whole trip in a single call'. It enumerates the exact categories and explicitly contrasts itself with per-topic siblings like get_flight_links, so an agent can clearly distinguish this aggregate tool from more detailed single-category tools.

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 says it is 'useful when a user is planning a trip end to end and wants every option in one place' and then names the alternative: 'Each per-topic tool ... returns richer detail and more guides for a single category.' This gives an agent an explicit when-to-use versus when-to-prefer-alternative decision rule.

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.