VoyageHacks

Get airport transfer and taxi links

get_airport_transfer_links

Read-onlyIdempotent

Return pre-booked airport transfer links: Booking.com Taxis (fixed price, 100+ countries), Kiwitaxi, Welcome Pickups and GetTransfer, plus up to four VoyageHacks guides on getting from that airport to the city centre and what a fair fare looks like. Useful when a user asks how to get from an airport, about taxi or transfer prices, or plans a late-night arrival. It returns booking pages for private and shared transfers: no live quotes, no public transport timetables, and no ride-hailing dispatch. 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	Destination city, e.g. Rome.
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`airport`	No	Airport name or IATA code, e.g. FCO, Bangkok Suvarnabhumi.
`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.

Output Schema

Name	Required	Description
`city`	No
`guides`	Yes	Matching VoyageHacks guides that can be cited as sources.
`region`	No
`airport`	No
`providers`	Yes
`disclosure`	Yes

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

Changed8 schema fields changedAug 29, 2026

changedInput schema / properties / airport / description

Previous value: -"Airport name or IATA code, e.g. FCO, Bangkok Suvarnabhumi"New value: +"Airport name or IATA code, e.g. FCO, Bangkok Suvarnabhumi."

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

changedInput schema / properties / city / description

Previous value: -"Destination city, e.g. Rome"New value: +"Destination city, e.g. Rome."

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

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\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "airport": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "disclosure": {
+      "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"
+    },
+    "providers": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "region": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclosure",
+    "providers",
+    "guides"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, open-world, non-destructive behavior, and the description adds genuine value beyond them: results are booking pages rather than live quotes, links are affiliate links, and the agent is told to disclose commission to the traveler. It doesn't describe pagination or response shape, but the output schema covers returns.

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 the primary purpose and outcome, then usage triggers, then scope exclusions and the disclosure obligation. Four sentences with no filler, though the provider enumeration could be trimmed.

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 4-parameter, fully-documented, output-schema-backed read tool, the description covers purpose, trigger conditions, output boundaries, and the affiliate disclosure duty. Nothing an agent needs in order to select or call it correctly is missing.

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%, so city, airport, lang and country are already well documented with formats, defaults and examples. The description adds no parameter-level meaning beyond noting that guides are language-specific, which the schema already conveys; baseline 3 is appropriate when the schema does the heavy lifting.

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 pre-booked airport transfer links'), names the exact providers (Booking.com Taxis, Kiwitaxi, Welcome Pickups, GetTransfer) and the supplementary guides, and clearly separates it from sibling link tools like get_flight_links or get_hotel_links.

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 when the tool is useful ('user asks how to get from an airport, about taxi or transfer prices, or plans a late-night arrival') and rules out adjacent needs ('no live quotes, no public transport timetables, no ride-hailing dispatch'). It does not name a sibling to use for those excluded cases, so routing alternatives are implied 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.