VoyageHacks

Get hotel search links for a city

get_hotel_links

Read-onlyIdempotent

Build a Booking.com search link for a city or property, with optional check-in and check-out dates, guest count and room count, plus an IHG brand search link (Holiday Inn, InterContinental, Crowne Plaza) and up to four VoyageHacks guides on the best areas and best-value stays there. The Booking.com link is regionalized to the traveler's country. Useful when a user asks where to stay, or about hotels, hostels or apartments in a place. It returns search links only: no live room rates, no availability check, no reviews and no reservation. 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, region or property name to search, e.g. Rome, Phuket, Hotel Kossak.
`lang`	No	Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
`rooms`	No	Number of rooms. Defaults to 1.
`adults`	No	Number of adults. Defaults to 2.
`checkin`	No	Check-in date, YYYY-MM-DD. Used only when checkout is also given.
`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.
`checkout`	No	Check-out date, YYYY-MM-DD.
`children`	No	Number of children. Defaults to 0.

Output Schema

TableJSON Schema

Name	Required	Description
`ihg`	No
`city`	No
`rooms`	No
`adults`	No
`guides`	Yes	Matching VoyageHacks guides that can be cited as sources.
`region`	No
`checkin`	No
`checkout`	No
`children`	No
`disclosure`	Yes
`hotelSearch`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedAug 29, 2026

changedInput schema / properties / adults / description

Previous value: -"Adults (default 2)"New value: +"Number of adults. Defaults to 2."

changedInput schema / properties / checkin / description

Previous value: -"Optional check-in date, YYYY-MM-DD"New value: +"Check-in date, YYYY-MM-DD. Used only when checkout is also given."

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

changedInput schema / properties / checkout / description

Previous value: -"Optional check-out date, YYYY-MM-DD"New value: +"Check-out date, YYYY-MM-DD."

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

addedInput schema / properties / children

Added value: +{
+  "description": "Number of children. Defaults to 0.",
+  "maximum": 10,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / city / description

Previous value: -"City, region or property name to search, e.g. Rome, Phuket"New value: +"City, region or property name to search, e.g. Rome, Phuket, Hotel Kossak."

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

changedInput schema / properties / rooms / description

Previous value: -"Rooms (default 1)"New value: +"Number of rooms. Defaults to 1."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "adults": {
+      "type": "integer"
+    },
+    "checkin": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "checkout": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "children": {
+      "type": "integer"
+    },
+    "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"
+    },
+    "hotelSearch": {
+      "type": "string"
+    },
+    "ihg": {
+      "type": "string"
+    },
+    "region": {
+      "type": "string"
+    },
+    "rooms": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "disclosure",
+    "hotelSearch",
+    "guides"
+  ],
+  "type": "object"
+}

First observedAug 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behavioral boundaries: it returns search links only, no live rates/availability/reviews/reservations, and the Booking.com link is regionalized to the traveler's country. It also surfaces the affiliate-disclosure requirement, which is valuable context an agent would otherwise miss. No contradiction with annotations.

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 compact and front-loaded with the core output, then adds regionalization, use case, limitations, and affiliate disclosure in separate sentences. Each sentence contributes distinct information with no filler.

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 tool with 8 optional parameters and an output schema, the description adequately covers what is returned, the scope of the result, the regionalization behavior, and important caveats. The existing output schema relieves the description from explaining return-value structure.

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%, with every parameter documented in the schema itself. The description adds a high-level mention of optional dates, guest count, and room count, but no parameter detail beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Build') and a clear resource: a Booking.com search link for a city or property, plus IHG brand links and VoyageHacks guides. It is clear on its own, but it does not explicitly differentiate itself from the sibling get_booking_links, so it stops short of a 5.

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 an explicit use case: 'Useful when a user asks where to stay, or about hotels, hostels or apartments in a place.' It does not name alternative tools or exclusion conditions, but the context is clear enough for an agent to select it for lodging-search requests.

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.