SlickTrip

Search hotels

search_hotels

Read-onlyIdempotent

Use when the traveler wants a place to stay for known dates. Returns hotels cheapest first with star class, guest rating, per-night and whole-stay price, hotel_ids and a search_key for track_hotel and hotel_price_calendar, and a search_url. Filters match the site: price, stars, guest rating, property kinds, amenities, free cancellation, hotels or vacation rentals, bedrooms (rentals), sort. Not for flexible months (add_hotel_bucket_list).

Input Schema

Name	Required	Description	Default
`sort`	No	Cheapest first, or best rated first.	price
`brand`	No	Only stays of this brand or chain, matched in the hotel's name. Put the city in location, the brand here.
`adults`	No	Adults. A hotel room prices up to 6 guests in all; vacation rentals up to 16.
`check_in`	Yes	YYYY-MM-DD.
`location`	Yes	A city, neighbourhood, landmark or hotel name.
`amenities`	No	Hotels: free parking, pool, gym, spa, free breakfast, beach access, pet-friendly, child-friendly, free wi-fi, air conditioning, all-inclusive, wheelchair accessible, ev charger, bar, restaurant, room service. Vacation rentals: kitchen, hot tub, fireplace, patio, grill, crib, beach access, pet-friendly, gym, air conditioning.
`check_out`	Yes	YYYY-MM-DD.
`min_stars`	No	Lowest star class to show, 1-5.
`max_results`	No	How many results to return, 1-50.
`min_bedrooms`	No	Vacation rentals with at least this many bedrooms, as the traveler said it ("a 5-bedroom house": 5). Searches vacation rentals; each home says its bedrooms, bathrooms and how many it sleeps.
`user_request`	No	Optional, and it works in the traveler's favor. Quote the traveler's latest message about this trip exactly as they wrote it, in their wording, language and spelling, not a summary. SlickTrip runs its own travel parser on these words: when a search fails or comes back empty, it compares what the traveler said with the arguments sent and returns a corrected search, so you can fix it without asking them again. It has caught Cancun sent as MEX instead of CUN, and travelers dropped from the party. A summary loses exactly the details it checks. If the message only answers a question ("yes, the 20th"), quote the message where they asked for the trip. Send the same quote on every call for this request. Leave out anything not about the trip, and never include names, contact details, or payment or ID information. The words also help SlickTrip improve its search.
`children_ages`	No	One age per child, 1-17.
`property_type`	No	Hotels, or vacation rentals.	hotel
`property_kinds`	No	Hotels: resort, boutique hotel, hostel, inn, motel, spa hotel, bed and breakfast, apartment hotel, beach hotel, ryokan. Vacation rentals: apartment, house, villa, cabin, cottage, chalet, bungalow, houseboat.
`min_guest_rating`	No	Lowest guest rating out of 5; 3.5, 4 or 4.5 work best. A rating out of 10 (8 and up) is read as half.
`free_cancellation`	No	Only stays with free cancellation.
`max_price_per_night`	No	Highest price per night to show, USD.
`min_price_per_night`	No	Lowest price per night to show, USD.

Output Schema

Name	Required	Description
`code`	No	On an error: a machine-readable kind, e.g. unknown_place
`note`	No	Prices are whole-stay; how to track
`field`	No	On unknown_place: which argument (origin, destination, ...)
`hotels`	No	Items: hotel_id, name, image, type, stars, guest_rating, reviews, per_night_usd, total_usd, amenities, description, hotel_url; vacation rentals add sleeps, bedrooms, bathrooms
`search`	No	location, check_in, check_out, adults, children_ages, nights, search_key
`status`	No	ok \| no_data \| error \| sign_in_required
`filters`	No	Applied filters: property_type, min_stars, free_cancellation, min_bedrooms, advanced, sort
`message`	No	Error or sign-in message from the server wrapper
`highlights`	No	The spread over every priced stay: cheapest, best_rated, cheapest_4_star_plus, most_reviewed; each with hotel_id, name, per_night_usd, total_usd, stars, guest_rating, reviews
`search_url`	No	slicktrip.com hotels search link
`searched_as`	No	What the search assumed: guests, hotels or vacation rentals
`suggestions`	No	On unknown_place: places to offer the traveler, each with code, name, kind (airport, all airports in the city, nearby airport), city, country
`total_found`	No	Total hotels found before max_results cut
`places_assumed`	No	Place names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 22, 2026

addedInput schema / properties / brand

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only stays of this brand or chain, matched in the hotel's name. Put the city in location, the brand here.",
+  "examples": [
+    "Four Seasons",
+    "Ritz-Carlton",
+    "Hilton"
+  ],
+  "title": "Brand"
+}

addedInput schema / properties / min_bedrooms

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 20,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Vacation rentals with at least this many bedrooms, as the traveler said it (\"a 5-bedroom house\": 5). Searches vacation rentals; each home says its bedrooms, bathrooms and how many it sleeps.",
+  "title": "Min Bedrooms"
+}

changedInput schema / properties / min_guest_rating / anyOf

Previous value: -[
-  {
-    "maximum": 5,
-    "minimum": 1,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 10,
+    "minimum": 1,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / min_guest_rating / description

Previous value: -"Lowest guest rating out of 5; 3.5, 4 or 4.5 work best."New value: +"Lowest guest rating out of 5; 3.5, 4 or 4.5 work best. A rating out of 10 (8 and up) is read as half."

changedOutput schema / properties / filters / description

Previous value: -"Applied filters: property_type, min_stars, free_cancellation, advanced, sort"New value: +"Applied filters: property_type, min_stars, free_cancellation, min_bedrooms, advanced, sort"

changedOutput schema / properties / hotels / description

Previous value: -"Items: hotel_id, name, image, type, stars, guest_rating, reviews, per_night_usd, total_usd, amenities, description, hotel_url"New value: +"Items: hotel_id, name, image, type, stars, guest_rating, reviews, per_night_usd, total_usd, amenities, description, hotel_url; vacation rentals add sleeps, bedrooms, bathrooms"

Changed3 schema fields changedOct 9, 2026

changedInput schema / properties / user_request / anyOf

Previous value: -[
-  {
-    "maxLength": 300,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 500,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / user_request / description

Previous value: -"Optional. The traveler's current travel request, briefly, in their own words. Used to interpret this search, suggest a corrected search if it fails, and improve SlickTrip's search. Include only this request; not earlier conversation, names, contact details, or payment or ID information."New value: +"Optional, and it works in the traveler's favor. Quote the traveler's latest message about this trip exactly as they wrote it, in their wording, language and spelling, not a summary. SlickTrip runs its own travel parser on these words: when a search fails or comes back empty, it compares what the traveler said with the arguments sent and returns a corrected search, so you can fix it without asking them again. It has caught Cancun sent as MEX instead of CUN, and travelers dropped from the party. A summary loses exactly the details it checks. If the message only answers a question (\"yes, the 20th\"), quote the message where they asked for the trip. Send the same quote on every call for this request. Leave out anything not about the trip, and never include names, contact details, or payment or ID information. The words also help SlickTrip improve its search."

changedInput schema / properties / user_request / examples

Previous value: -[
-  "cheap nonstop to Lisbon early May",
-  "family of 8 in Albufeira, 4 nights mid November"
-]New value: +[
+  "we're 6 friends from madrid, want somewhere cheap and fun in europe dec 20-24, morning flights pls",
+  "necesito llevar a mi mamá de Calgary a Kolkata a fines de octubre, no puede hacer escala en Estados Unidos"
+]

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, open-world search. The description adds useful behavioral context beyond that: results are cheapest first, include star class, guest rating, per-night and whole-stay price, hotel_ids, search_key, and search_url, and the search_key feeds track_hotel and hotel_price_calendar. It does not discuss failure modes or pagination, but the added return-format and follow-on-tool context is substantial.

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 use case, then return behavior, then filter scope, then a clear exclusion. Despite being dense, every sentence adds routing or behavioral value, and the sibling exclusion is placed where it is most useful.

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?

With 18 parameters, full schema descriptions, an output schema, and rich annotations, the description supplies the remaining context an agent needs: when to use it, what it returns, how results are ordered, and which sibling handles a different case. Nothing essential for correct invocation 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 every parameter is already documented in the schema, including filter enums, ranges, and examples. The description adds only a high-level enumeration of filter categories ('price, stars, guest rating, property kinds, amenities, free cancellation, hotels or vacation rentals, bedrooms, sort') and does not add syntax or semantics beyond the schema. This meets the baseline for fully covered schemas.

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 (search hotels) plus the precise condition for use: known dates. It also distinguishes this tool from add_hotel_bucket_list for flexible-month searches, so the agent can route correctly without opening the schema.

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?

It explicitly says when to use the tool ('traveler wants a place to stay for known dates') and when not to use it ('Not for flexible months'), naming the alternative sibling tool. No inference is required.

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

All SlickTrip 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?