VoyageHacks

Get flight search links for a route

get_flight_links

Read-onlyIdempotent

Build a flight search link on Booking.com Flights for a route and optional dates, and return up to four VoyageHacks guides on fares, budget airlines and baggage rules for that trip. Pass origin and destination as IATA codes for a prefilled route search; without both, the link opens the general flight search page. Also returns a delayed or cancelled flight compensation link (AirHelp), a Vueling link for short-haul Europe, and, when the route touches their hubs, direct links for Air Serbia (Belgrade) and Air India. The Booking.com link is regionalized to the traveler's country. Useful when a trip involves air travel and the user wants somewhere to compare fares. It returns search links only: no live fares, seat availability or schedules, no booking and no airport transfers. 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
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`origin`	No	Origin IATA city or airport code, e.g. LON, NYC, BER.
`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.
`passengers`	No	Number of adult passengers. Defaults to 1.
`depart_date`	No	Outbound date, YYYY-MM-DD. Omitted dates default to about a month ahead.
`destination`	No	Destination IATA city or airport code, e.g. HKT, TYO, ROM.
`return_date`	No	Return date, YYYY-MM-DD. Omit for a one-way search.

Output Schema

Name	Required	Description
`route`	No
`guides`	Yes	Matching VoyageHacks guides that can be cited as sources.
`region`	No
`vueling`	No
`airIndia`	No
`airSerbia`	No
`disclosure`	Yes
`flightSearch`	Yes
`virginAtlantic`	No
`flightCompensation`	No

Schema Changelog

Changes observed during successful MCP inspections.

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"
+]

Changed1 schema field changedOct 1, 2026
- addedOutput schema / properties / virginAtlantic
```
Added value: +{
+  "type": "string"
+}
```

Changed13 schema fields changedAug 29, 2026

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}$"
```

changedInput schema / properties / depart_date / description

Previous value: -"Optional outbound date, YYYY-MM-DD"New value: +"Outbound date, YYYY-MM-DD. Omitted dates default to about a month ahead."

addedInput schema / properties / depart_date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

changedInput schema / properties / destination / description

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

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

changedInput schema / properties / lang / description

Previous value: -"Content language for the guides that come back (default \"en\")"New value: +"Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to \"en\"."

changedInput schema / properties / origin / description

Previous value: -"Origin IATA city/airport code, e.g. LON, NYC, BER"New value: +"Origin IATA city or airport code, e.g. LON, NYC, BER."

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

changedInput schema / properties / passengers / description

Previous value: -"Passengers (default 1)"New value: +"Number of adult passengers. Defaults to 1."

changedInput schema / properties / return_date / description

Previous value: -"Optional return date, YYYY-MM-DD (omit for one-way)"New value: +"Return date, YYYY-MM-DD. Omit for a one-way search."

addedInput schema / properties / return_date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "airIndia": {
+      "type": "string"
+    },
+    "airSerbia": {
+      "type": "string"
+    },
+    "disclosure": {
+      "type": "string"
+    },
+    "flightCompensation": {
+      "type": "string"
+    },
+    "flightSearch": {
+      "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"
+    },
+    "region": {
+      "type": "string"
+    },
+    "route": {
+      "type": "object"
+    },
+    "vueling": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclosure",
+    "flightSearch",
+    "guides"
+  ],
+  "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?

With annotations already declaring readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral detail: IATA prefill behavior, what happens without origin and destination, regionalization of the Booking.com link, additional compensation and airline links, affiliate disclosure, and a clear boundary that no live fares, bookings, or transfers are returned.

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 main purpose and key constraints are front-loaded, and the description is structured around what is returned and what is not. It is somewhat dense and lists multiple airline-specific links, but those details are relevant to the tool's output and affiliate disclosure obligations.

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?

For a high-complexity link-generation tool with seven optional parameters and an output schema, the description is complete enough: it explains the returned link types, the guides, regionalization behavior, limitations, and affiliate disclosure. The output schema can carry the exact return structure.

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 schema already documents all seven parameters. The description still adds useful context about origin and destination being IATA codes for a prefilled route search and about omitted dates or missing route codes affecting the generated link, though it does not elaborate on parameters like passengers or lang.

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-and-resource: building Booking.com flight search links for a route with optional dates, plus VoyageHacks guides. It clearly distinguishes this from sibling link-builder tools by naming flights rather than hotels, cars, transfers, or bookings.

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?

It gives a clear usage condition: useful when a trip involves air travel and the user wants to compare fares. It also clarifies the main limitation (search links only, no live fares or booking), though it does not explicitly route the agent to alternatives such as get_hotel_links or get_airport_transfer_links.

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.