PriceWin

Search Hotels Live

search_hotels_live

Starts a live hotel search for a city and date range. Prices come from Agoda, Booking.com, Traveloka, Trip.com, Hotels.com and Airbnb, plus direct rates from OpenTravel partner hotels. Returns a session ID; poll_search_results returns the results as they arrive. Optional filters narrow the results by hotel name, area or total price for the stay. Prices depend on the party: it defaults to 2 adults in 1 room, and the result states the party searched and flags when it was defaulted. When the city or dates are missing, the result is a question for the user instead of a search; the stay dates searched are echoed back for confirmation.

Input Schema

Name	Required	Description
`area`	No	Optional ward, neighbourhood, beach or landmark within the city, e.g. 'Shoreditch' with city 'London'. A place the search recognises lists the hotels within a few km of it; otherwise it filters the city's hotels by their address.
`city`	No	City or broad destination, e.g. 'Da Nang'. When omitted, the result asks the user for it.
`rooms`	No	Number of rooms (default 1).
`adults`	No	Number of adults (default 2). Prices depend on it.
`checkIn`	No	Check-in date (YYYY-MM-DD), today or later. When omitted, the result asks the user for it.
`checkOut`	No	Check-out date (YYYY-MM-DD), after checkIn. When omitted, the result asks the user for it.
`children`	No	Number of children sharing the room (default 0). Child ages determine family quotes; sources without verified occupancy support are omitted.
`language`	No	Preferred UI language (en/vi/de/ja/ko/zh/fr/es/ru/th/id).
`priceMax`	No	Maximum total price for the whole stay (not per night), in priceCurrency.
`priceMin`	No	Minimum total price for the whole stay (not per night), in priceCurrency.
`amenities`	No	Optional amenities every hotel shown must have, as at least one of its sites lists them: pool, beach, breakfast, parking, gym, spa, airport_shuttle, kitchen, family (family rooms).
`childAges`	No	Age of each child, 0–17. Family quotes are limited to sources that accept this occupancy; unsupported sources are omitted.
`hotelName`	No	Optional hotel-name filter when the user names a specific property
`queryText`	No	Optional short excerpt of the current request, used only to detect the UI language; it is not stored or forwarded.
`priceCurrency`	No	ISO 4217 code of priceMin/priceMax (USD, EUR, VND, …); defaults to the currency of the UI language.

Output Schema

Name	Required	Description	Default
`city`	Yes
`tier`	Yes
`limit`	Yes
`cached`	No
`hotels`	Yes
`nights`	Yes
`offset`	Yes
`status`	Yes
`checkIn`	Yes
`fxRates`	Yes
`hasMore`	Yes
`checkOut`	Yes
`language`	No
`progress`	Yes
`sessionId`	No
`agodaStatus`	Yes
`totalHotels`	Yes
`bookingStatus`	Yes
`longStayNotice`	No
`travelokaStatus`	Yes
`opentravelStatus`	Yes
`tier2AgodaStatus`	Yes
`opentravelResults`	Yes
`tier2BookingStatus`	Yes
`tier2TravelokaStatus`	Yes
`opentravelIndicativeResults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedInput schema / properties / childAges

Added value: +{
+  "description": "Age of each child, 0–17. Family quotes are limited to sources that accept this occupancy; unsupported sources are omitted.",
+  "items": {
+    "maximum": 17,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

changedInput schema / properties / children / description

Previous value: -"Number of children sharing the room (default 0). OTA prices cannot include children; the result says so when children are given."New value: +"Number of children sharing the room (default 0). Child ages determine family quotes; sources without verified occupancy support are omitted."

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / area / description

Previous value: -"Optional district, ward, or neighborhood filter within the city"New value: +"Optional ward, neighbourhood, beach or landmark within the city, e.g. 'Shoreditch' with city 'London'. A place the search recognises lists the hotels within a few km of it; otherwise it filters the city's hotels by their address."

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / amenities

Added value: +{
+  "description": "Optional amenities every hotel shown must have, as at least one of its sites lists them: pool, beach, breakfast, parking, gym, spa, airport_shuttle, kitchen, family (family rooms).",
+  "items": {
+    "enum": [
+      "pool",
+      "beach",
+      "breakfast",
+      "parking",
+      "gym",
+      "spa",
+      "airport_shuttle",
+      "kitchen",
+      "family"
+    ],
+    "type": "string"
+  },
+  "maxItems": 9,
+  "type": "array"
+}

Changed1 schema field changedOct 17, 2026
- addedOutput schema / properties / hotels / items / properties / prices / properties / airbnb
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
Changed5 schema fields changedOct 12, 2026
- addedOutput schema / properties / hotels / items / properties / prices / properties / expedia
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / hotelscom
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / official
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / priceline
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / tripcom
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
First observedOct 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: it returns a session ID rather than results, results must be polled, the party defaults to 2 adults in 1 room and the response flags when defaulting happened, and missing city/dates produce a clarifying question instead of a search. The echoed stay dates are also disclosed, which is exactly the kind of confirmation behavior annotations cannot convey.

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 purpose and the polling contract, then defaults and the missing-input behavior. Every sentence carries information, though the final sentence on echoing stay dates is slightly wordier than needed.

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 15-parameter asynchronous search tool with an output schema, the description covers the essential non-schema contract: session-ID return, polling, defaulted party flagging, and the clarification-on-missing-input path. Nothing an agent needs to invoke it correctly is absent.

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 coverage is 100% and every parameter is already documented, including currency, total-vs-per-night pricing and child-age constraints. The description mostly restates those (party defaults, name/area/price filters) rather than adding new syntax or interplay, so the baseline 3 applies.

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 ('starts a live hotel search') with the scoped resources (city and date range) and names the source network plus the follow-up sibling poll_search_results. An agent can distinguish this from get_hotel_detail, compare_hotel_link and search_flights_live without opening any schema.

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?

The two-step workflow is explicit: start the search here, then call poll_search_results as results arrive. It also describes the fallback path when city or dates are missing. It stops short of naming when-not-to-use or pointing to alternative hotel tools, so it is clear context without exclusions.

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

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