Skiplagged MCP

Skiplagged Hotel Search

sk_hotels_search

Read-only

Search Skiplagged for hotels in a city with specific check-in and check-out dates, including ratings and pricing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>",
      "checkin": "<checkin>",
      "checkout": "<checkout>"
    },
    "name": "sk_hotels_search"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	City name to search for hotels (will be matched against available cities)
`sort`	No	Sort hotels by price (cheapest first), ranking (highest rated first), value (best value rating), or discount (best deals first, default when deals available)	value
`limit`	No	Maximum number of hotels to return (default: 12, max: 100)
`offset`	No	Number of hotels to skip (default: 0); limit + offset must not exceed 100
`checkin`	Yes	Check-in date (YYYY-MM-DD format)
`checkout`	Yes	Check-out date (YYYY-MM-DD format)
`currency`	No	Currency to show prices in (ISO 4217, default: USD). Pass the user's local currency when you know it, e.g. GBP for a UK user or EUR for a user in Germany. Prices are converted from USD and are approximate; sorting and booking links are unaffected.
`numRooms`	No	Number of rooms (default: 1, max: 9)
`numAdults`	No	Number of adults (default: 2, max: 10)
`numChildren`	No	Number of children (default: 0, max: 10)

Output Schema

Name	Required	Description
`pricing`	No	Currency used for `results[].price`
`results`	Yes
`searchUrl`	Yes	Complete search URL with all parameters
`pagination`	Yes	Result pagination information

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / offset / description

Previous value: -"Number of hotels to skip for pagination (default: 0)"New value: +"Number of hotels to skip (default: 0); limit + offset must not exceed 100"

Changed18 schema fields changedOct 30, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / checkout / $ref
```
Removed value: -"#/properties/checkin"
```
addedInput schema / properties / checkout / type
```
Added value: +"string"
```

addedInput schema / properties / currency

Added value: +{
+  "description": "Currency to show prices in (ISO 4217, default: USD). Pass the user's local currency when you know it, e.g. GBP for a UK user or EUR for a user in Germany. Prices are converted from USD and are approximate; sorting and booking links are unaffected.",
+  "enum": [
+    "USD",
+    "AUD",
+    "BRL",
+    "CAD",
+    "CHF",
+    "CNY",
+    "CZK",
+    "DKK",
+    "EUR",
+    "GBP",
+    "HKD",
+    "IDR",
+    "INR",
+    "JPY",
+    "KRW",
+    "MXN",
+    "MYR",
+    "PLN",
+    "RON",
+    "SEK",
+    "SGD",
+    "TRY",
+    "TWD",
+    "UAH",
+    "VND"
+  ],
+  "type": "string"
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / pagination / properties / currentlyShowing / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / pagination / properties / currentlyShowing / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / pagination / properties / limit / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / pagination / properties / limit / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / pagination / properties / offset / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / pagination / properties / offset / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / pagination / properties / totalAvailable / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / pagination / properties / totalAvailable / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / pricing

Added value: +{
+  "additionalProperties": false,
+  "description": "Currency used for `results[].price`",
+  "properties": {
+    "approximate": {
+      "description": "True when prices were converted from USD; the final charge on the booking site may differ",
+      "type": "boolean"
+    },
+    "currency": {
+      "description": "ISO 4217 code the prices are shown in",
+      "type": "string"
+    },
+    "notice": {
+      "description": "Short note to relay to the user about the shown currency",
+      "type": "string"
+    },
+    "rate": {
+      "description": "Units of `currency` per 1 USD used for conversion (1 for USD)",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "rateAsOf": {
+      "description": "When the server fetched the exchange rate (ISO datetime)",
+      "type": "string"
+    },
+    "requestedCurrency": {
+      "description": "ISO 4217 code the caller asked for (may differ on fallback)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "currency",
+    "requestedCurrency",
+    "rate",
+    "approximate"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / price / properties / amount / description
```
Added value: +"Nightly price in `currency` (converted from USD)"
```
addedOutput schema / properties / results / items / properties / price / properties / currency / description
```
Added value: +"ISO 4217 code of `amount`"
```

addedOutput schema / properties / results / items / properties / price / properties / usdAmount

Added value: +{
+  "description": "Source nightly price in US dollars; use it for comparison",
+  "type": "number"
+}

Changed9 schema fields changedAug 17, 2026

removedInput schema / properties / checkin / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```
addedInput schema / properties / checkout / $ref
```
Added value: +"#/properties/checkin"
```
removedInput schema / properties / checkout / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```
removedInput schema / properties / checkout / type
```
Removed value: -"string"
```
addedInput schema / properties / city / minLength
```
Added value: +1
```
addedInput schema / properties / offset / maximum
```
Added value: +99
```

removedInput schema / properties / renderMode

Removed value: -{
-  "description": "Preferred render mode for tool output (ui or text).",
-  "enum": [
-    "ui",
-    "text"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / results / items / properties / _meta

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "uiResourceType": {
-      "const": "HotelCard",
-      "type": "string"
-    }
-  },
-  "required": [
-    "uiResourceType"
-  ],
-  "type": "object"
-}

addedOutput schema / properties / results / items / properties / id / description
```
Added value: +"Hotel result card identifier; not a user identifier"
```

Changed1 schema field changedFeb 23, 2026

addedInput schema / properties / renderMode

Added value: +{
+  "description": "Preferred render mode for tool output (ui or text).",
+  "enum": [
+    "ui",
+    "text"
+  ],
+  "type": "string"
+}

First observedJan 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that results include ratings and pricing; it says nothing about pagination ceilings or the currency conversion behavior, which are the notable quirks of this tool and live only in the schema.

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?

A single grammatical sentence with the essential inputs and outputs front-loaded and no filler. It is efficient, though it omits context that could have earned the remaining space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

With an output schema and full parameter documentation, the structured data carries most of the load, so the terse description is not disqualifying. Still, for a 10-parameter search tool with a city-matching quirk and a sibling detail tool, one clarifying sentence about city resolution or follow-up would have made it complete.

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 all ten parameters including the sort enum, currency list, and limit/offset constraints are already fully documented. The description only echoes that dates are required, adding no meaning beyond the schema, so the baseline 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 names a specific verb (Search) and resource (hotels) on a named provider and states what is returned (ratings and pricing) plus the required date inputs. It implicitly distinguishes itself from the sibling sk_hotel_details, but never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as sk_hotel_details for a specific property or sk_resolve_location for ambiguous city names. An agent must infer from the name alone that this is the discovery step.

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

All Skiplagged MCP 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.

Resources

Need Help?