The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
Shows cheapest one-way flight prices across a date range. Returns daily prices with price band thresholds for comparison. Use with origin/destination IATA codes from places_find_location. Defaults to next 6 months if no dates provided.
The description explains the capability, when to use it, and what to expect.
Inputs86/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
origin
Departure city IATA code (e.g., LON, NYC, SIN)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
destination
Arrival city IATA code (e.g., BKK, PAR, TYO)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
startDate
Start date (YYYY-MM-DD). Defaults to today.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
endDate
End date (YYYY-MM-DD). Defaults to 6 months from start.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
directOnly
Show direct flights only
Clear enough to supply this argument.
locale
Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar').
Clear enough to supply this argument.
currencyCode
The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "flights_one_way_price",
"title": "Flight One-Way Price",
"description": "Shows cheapest one-way flight prices across a date range. Returns daily prices with price band thresholds for comparison. Use with origin/destination IATA codes from places_find_location. Defaults to next 6 months if no dates provided.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"origin",
"destination",
"currencyCode"
],
"properties": {
"locale": {
"type": "string",
"description": "Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar')."
},
"origin": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Departure city IATA code (e.g., LON, NYC, SIN)"
},
"endDate": {
"$ref": "#/properties/startDate",
"description": "End date (YYYY-MM-DD). Defaults to 6 months from start."
},
"startDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date (YYYY-MM-DD). Defaults to today."
},
"directOnly": {
"type": "boolean",
"default": false,
"description": "Show direct flights only"
},
"destination": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Arrival city IATA code (e.g., BKK, PAR, TYO)"
},
"currencyCode": {
"type": "string",
"description": "The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Gets the current published timetable of nonstop flights between two cities: airlines, flight numbers, departure and arrival airports and times, duration, and operating periods (dates, weekdays and aircraft). Connecting flights are not listed: use flights_search for those and for fares on a date. Accepts city or airport IATA codes from places_find_location; an airport code gives its city's timetable. Results are paged: when metadata.hasMore is true, call again with page + 1. Optionally filter by airline code.
The description explains the capability, when to use it, and what to expect.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
from
Departure city or airport code (IATA, e.g., 'SIN' or 'LHR'). An airport code gives its city's timetable.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
to
Arrival city or airport code (IATA, e.g., 'BKK' or 'LHR'). An airport code gives its city's timetable.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
page
Page of flights, 1-based (default 1). Rarely needed: most routes fit on one page.
Clear enough to supply this argument.
pageSize
Flights per page (default and max 200). Use it to narrow a long answer.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar').
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "flights_schedule",
"title": "Flight Schedule",
"description": "Gets the current published timetable of nonstop flights between two cities: airlines, flight numbers, departure and arrival airports and times, duration, and operating periods (dates, weekdays and aircraft). Connecting flights are not listed: use flights_search for those and for fares on a date. Accepts city or airport IATA codes from places_find_location; an airport code gives its city's timetable. Results are paged: when metadata.hasMore is true, call again with page + 1. Optionally filter by airline code.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Arrival city or airport code (IATA, e.g., 'BKK' or 'LHR'). An airport code gives its city's timetable."
},
"from": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Departure city or airport code (IATA, e.g., 'SIN' or 'LHR'). An airport code gives its city's timetable."
},
"page": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "Page of flights, 1-based (default 1). Rarely needed: most routes fit on one page."
},
"locale": {
"type": "string",
"description": "Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar')."
},
"airline": {
"type": "string",
"pattern": "^[A-Z0-9]{2}$",
"description": "Optional: Filter by airline code (2-letter IATA code, e.g., 'EK', 'SQ')"
},
"pageSize": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Flights per page (default and max 200). Use it to narrow a long answer."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Searches for flights between airports or cities. Not for flight status, price tracking, visa information, bookings, or reservation management.
Polling flow:
1. First call with newSearch → creates search session, returns searchId immediately (status: "created", pollAgainInSeconds: 5).
2. Wait pollAgainInSeconds, then call again with searchId → returns flight results with status "incomplete" (cheaper fares still arriving, pollAgainInSeconds says when to call again) or "complete" (final results).
3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop when status is "complete". If it is still "incomplete" after 3 reads, use the results you have.
A search is complete about 30 seconds after it is created. After that, every read (another page, new filters or sorting) returns status "complete" at once.
Parameters:
- newSearch: Route (from/to as IATA codes), dates (fromDate, toDate in YYYY-MM-DD), passengers, and cabin class. Omit toDate for one-way trips.
- Defaults when not specified: 1 adult, 0 children, 0 infants, economy cabin.
- filters: Include only when the user mentions specific preferences (airlines, stops, times, price range, etc.).
- sorting: A single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_departure_time_asc/desc (return departure, round-trip only).
- page, pageSize: Which page of the ranked trips a searchId read returns. page 1-100 (default 1), pageSize 1-50 (default 20). Out-of-range values are rejected.
Paging: every searchId read returns metadata {page, pageSize, resultCount, totalCandidates, hasMore}. totalCandidates counts trips matching the filters across all pages; resultCount counts this page. For more trips, repeat the searchId with the same filters and sorting and page + 1 while hasMore is true. Featured trips appear on page 1 only, and labels (best_value, cheapest, cheapest_direct) are judged over all matching trips, not the page.
Time filtering (two approaches, mutually exclusive per dimension):
1. Time blocks (6-hour windows) — for broad preferences:
- Options: "midnight" (12am-6am), "morning" (6am-12pm), "afternoon" (12pm-6pm), "night" (6pm-12am)
- Example: outboundDepartureTimeBlocks: ["morning", "afternoon"] = depart before 6pm
2. Time ranges (minute precision) — for specific time requests:
- Format: {min: minutesFromMidnight, max: minutesFromMidnight}, range 0-1440
- Example: "flights after 10pm" → outboundDepartureTimeRange: {min: 1320, max: 1440}
- Example: "depart 8am-1pm" → outboundDepartureTimeRange: {min: 480, max: 780}
- Supports wraparound: {min: 1380, max: 60} = 11pm-1am (crosses midnight)
Time blocks and time ranges cannot both be specified for the same dimension (e.g., outboundDeparture).
Refinement: Provide the searchId from a previous response with updated filters or sorting. Refinement replaces all previous filters and sorting entirely — include existing values alongside new ones to preserve them.
Example — changing return to after 10pm while keeping existing airlines ["SQ", "KE"], outbound 6am-8am, and price_asc sorting:
{ "searchId": "abc", "filters": { "airlines": ["SQ", "KE"], "outboundDepartureTimeRange": { "min": 360, "max": 480 }, "inboundArrivalTimeRange": { "min": 1320, "max": 1440 } }, "sorting": "price_asc" }
Default behavior:
- One date provided → one-way trip
- Return date mentioned → round-trip
- No preferences stated → omit filters
- Specific time requested (e.g., "after 10pm") → use time range
- Broad time preference (e.g., "morning flights") → use time blocks
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
searchId
Reuse the searchId from a previous search when refining, filtering, sorting, or selecting.
Clear enough to supply this argument.
newSearch › from
Departure IATA code (required for a new search when searchId is omitted).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › to
Arrival IATA code (required for a new search when searchId is omitted).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › fromDate
Departure date in YYYY-MM-DD (required for a new search when searchId is omitted).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › toDate
Return date in YYYY-MM-DD for round-trip searches. Omit entirely for one-way trips (do not send null or empty string).
Clear enough to supply this argument.
newSearch › adultsCount
Number of adult passengers (18+). Default: 1. Example: 'my wife and I' = 2 adults
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › childrenCount
Number of child passengers (2-17). Default: 0. Example: 'with my 5-year-old' = 1 child
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › infantsCount
Number of infant passengers (under 2 years). Default: 0. Typically on parent's lap
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
newSearch › cabinClass
Requested cabin class for the search
Explain the meaning of this value, not just its name.
filters › airlines
2-letter IATA airline codes. e.g. ['SQ', 'UA', 'LH']
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › alliances
Airline alliances. e.g. ['star_alliance', 'oneworld', 'skyteam']
Clear enough to supply this argument.
filters › stops
Number of stops. e.g. Direct flight = 0, 1 stop = [1], direct or 1 stop = [0, 1]
Clear enough to supply this argument.
filters › flightExperiences
Flight experience preferences. e.g. ['no_overnight_flight', 'no_long_stopover']
Clear enough to supply this argument.
filters › originAirports
Filter by specific departure airports. e.g. ['JFK']
Clear enough to supply this argument.
filters › destinationAirports
Filter by specific arrival airports. e.g. ['CDG']
Clear enough to supply this argument.
filters › stopoverAirports
Include flights with layovers at these airports. e.g. ['DXB']
Clear enough to supply this argument.
filters › priceRange › min
Minimum price per person
Clear enough to supply this argument.
filters › priceRange › max
Maximum price per person
Clear enough to supply this argument.
filters › outboundDepartureTimeBlocks
Filter outbound departure times. Use this to specify when you want to depart on the outgoing flight. e.g. ['morning', 'afternoon'] for departures before 6pm
Clear enough to supply this argument.
filters › outboundArrivalTimeBlocks
Filter outbound arrival times. Use this to specify when you want to arrive at your destination. e.g. ['morning', 'afternoon'] for arrivals before 6pm
Clear enough to supply this argument.
filters › inboundDepartureTimeBlocks
Filter return flight departure times for ROUND-TRIP searches. Use this to specify when you want the return leg to depart. e.g. ['morning', 'afternoon'] for departures before 6pm
Clear enough to supply this argument.
filters › inboundArrivalTimeBlocks
Filter return flight arrival times for ROUND-TRIP searches. Use this to specify when you want the return leg to arrive back. e.g. ['morning', 'afternoon'] for arrivals before 6pm
Clear enough to supply this argument.
filters › outboundDepartureTimeRange › min
Start time in minutes from midnight (0-1439). Example: 480 = 8:00 AM
Resolve the mismatch between this description and its schema constraints.
filters › outboundDepartureTimeRange › max
End time in minutes from midnight (0-1440). Example: 780 = 1:00 PM. Supports max=1440 for end-of-day (midnight). For midnight wraparound (e.g., 11pm-1am), max can be less than min.
Resolve the mismatch between this description and its schema constraints.
filters › bookingTypes
Booking channel - Book on Wego or direct with airline. e.g. ['wego', 'airline']
Clear enough to supply this argument.
filters › bookingSites
Filter by specific travel booking sites. e.g. ['booking.com']
Clear enough to supply this argument.
filters › outboundTotalDurationRange › min
Minimum duration in minutes
Explain the meaning of this value, not just its name.
filters › outboundTotalDurationRange › max
Maximum duration in minutes
Explain the meaning of this value, not just its name.
filters › inboundTotalDurationRange › min
Minimum duration in minutes
Explain the meaning of this value, not just its name.
filters › inboundTotalDurationRange › max
Maximum duration in minutes
Explain the meaning of this value, not just its name.
sorting
Sort order for results. Pass a single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_departure_time_asc/desc (return departure, round-trip only).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar').
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
currencyCode
The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
siteCode
The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come from. Do NOT take it from the departure, arrival or hotel city: a user in India searching London is still 'IN'. Omit it when unknown (default 'US'). Set it when the search is created; a searchId read keeps the search's site.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
page
Page of trips a searchId read returns, 1-based (default 1, max 100).
Clear enough to supply this argument.
pageSize
Trips per page on a searchId read (default 20, max 50). Out-of-range or non-integer values are rejected, never clamped.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "flights_search",
"title": "Search Flights",
"description": "Searches for flights between airports or cities. Not for flight status, price tracking, visa information, bookings, or reservation management.\n\nPolling flow:\n1. First call with newSearch → creates search session, returns searchId immediately (status: \"created\", pollAgainInSeconds: 5).\n2. Wait pollAgainInSeconds, then call again with searchId → returns flight results with status \"incomplete\" (cheaper fares still arriving, pollAgainInSeconds says when to call again) or \"complete\" (final results).\n3. While status is \"incomplete\", wait pollAgainInSeconds and call again. Stop when status is \"complete\". If it is still \"incomplete\" after 3 reads, use the results you have.\n\nA search is complete about 30 seconds after it is created. After that, every read (another page, new filters or sorting) returns status \"complete\" at once.\n\nParameters:\n- newSearch: Route (from/to as IATA codes), dates (fromDate, toDate in YYYY-MM-DD), passengers, and cabin class. Omit toDate for one-way trips.\n- Defaults when not specified: 1 adult, 0 children, 0 infants, economy cabin.\n- filters: Include only when the user mentions specific preferences (airlines, stops, times, price range, etc.).\n- sorting: A single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_departure_time_asc/desc (return departure, round-trip only).\n- page, pageSize: Which page of the ranked trips a searchId read returns. page 1-100 (default 1), pageSize 1-50 (default 20). Out-of-range values are rejected.\n\nPaging: every searchId read returns metadata {page, pageSize, resultCount, totalCandidates, hasMore}. totalCandidates counts trips matching the filters across all pages; resultCount counts this page. For more trips, repeat the searchId with the same filters and sorting and page + 1 while hasMore is true. Featured trips appear on page 1 only, and labels (best_value, cheapest, cheapest_direct) are judged over all matching trips, not the page.\n\nTime filtering (two approaches, mutually exclusive per dimension):\n1. Time blocks (6-hour windows) — for broad preferences:\n - Options: \"midnight\" (12am-6am), \"morning\" (6am-12pm), \"afternoon\" (12pm-6pm), \"night\" (6pm-12am)\n - Example: outboundDepartureTimeBlocks: [\"morning\", \"afternoon\"] = depart before 6pm\n\n2. Time ranges (minute precision) — for specific time requests:\n - Format: {min: minutesFromMidnight, max: minutesFromMidnight}, range 0-1440\n - Example: \"flights after 10pm\" → outboundDepartureTimeRange: {min: 1320, max: 1440}\n - Example: \"depart 8am-1pm\" → outboundDepartureTimeRange: {min: 480, max: 780}\n - Supports wraparound: {min: 1380, max: 60} = 11pm-1am (crosses midnight)\n\nTime blocks and time ranges cannot both be specified for the same dimension (e.g., outboundDeparture).\n\nRefinement: Provide the searchId from a previous response with updated filters or sorting. Refinement replaces all previous filters and sorting entirely — include existing values alongside new ones to preserve them.\n\nExample — changing return to after 10pm while keeping existing airlines [\"SQ\", \"KE\"], outbound 6am-8am, and price_asc sorting:\n{ \"searchId\": \"abc\", \"filters\": { \"airlines\": [\"SQ\", \"KE\"], \"outboundDepartureTimeRange\": { \"min\": 360, \"max\": 480 }, \"inboundArrivalTimeRange\": { \"min\": 1320, \"max\": 1440 } }, \"sorting\": \"price_asc\" }\n\nDefault behavior:\n- One date provided → one-way trip\n- Return date mentioned → round-trip\n- No preferences stated → omit filters\n- Specific time requested (e.g., \"after 10pm\") → use time range\n- Broad time preference (e.g., \"morning flights\") → use time blocks",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"currencyCode"
],
"properties": {
"page": {
"type": "integer",
"default": 1,
"maximum": 100,
"minimum": 1,
"description": "Page of trips a searchId read returns, 1-based (default 1, max 100)."
},
"locale": {
"type": "string",
"description": "Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar')."
},
"filters": {
"type": "object",
"properties": {
"stops": {
"type": "array",
"items": {
"type": "number",
"description": "Number of stops"
},
"description": "Number of stops. e.g. Direct flight = 0, 1 stop = [1], direct or 1 stop = [0, 1]"
},
"airlines": {
"type": "array",
"items": {
"type": "string",
"maxLength": 2,
"description": "2-letter IATA airline code"
},
"description": "2-letter IATA airline codes. e.g. ['SQ', 'UA', 'LH']"
},
"alliances": {
"type": "array",
"items": {
"enum": [
"star_alliance",
"oneworld",
"skyteam"
],
"type": "string"
},
"description": "Airline alliances. e.g. ['star_alliance', 'oneworld', 'skyteam']"
},
"priceRange": {
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Maximum price per person"
},
"min": {
"type": "number",
"description": "Minimum price per person"
}
},
"description": "Budget filter (e.g., 'under $500' = {max: 500}). Per-person price in user's currency.",
"additionalProperties": false
},
"bookingSites": {
"type": "array",
"items": {
"type": "string",
"description": "Travel booking site"
},
"description": "Filter by specific travel booking sites. e.g. ['booking.com']"
},
"bookingTypes": {
"type": "array",
"items": {
"enum": [
"wego",
"airline"
],
"type": "string"
},
"description": "Booking channel - Book on Wego or direct with airline. e.g. ['wego', 'airline']"
},
"originAirports": {
"type": "array",
"items": {
"type": "string",
"description": "Departure IATA airport code"
},
"description": "Filter by specific departure airports. e.g. ['JFK']"
},
"stopoverAirports": {
"type": "array",
"items": {
"type": "string",
"description": "Stopover/Transit IATA airport code"
},
"description": "Include flights with layovers at these airports. e.g. ['DXB']"
},
"flightExperiences": {
"type": "array",
"items": {
"enum": [
"no_overnight_flight",
"no_long_stopover"
],
"type": "string"
},
"description": "Flight experience preferences. e.g. ['no_overnight_flight', 'no_long_stopover']"
},
"destinationAirports": {
"type": "array",
"items": {
"type": "string",
"description": "Arrival IATA airport code"
},
"description": "Filter by specific arrival airports. e.g. ['CDG']"
},
"inboundArrivalTimeRange": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeRange",
"description": "Granular return arrival time range in minutes from midnight for ROUND-TRIP searches. Cannot be used with inboundArrivalTimeBlocks."
},
"inboundArrivalTimeBlocks": {
"type": "array",
"items": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeBlocks/items"
},
"description": "Filter return flight arrival times for ROUND-TRIP searches. Use this to specify when you want the return leg to arrive back. e.g. ['morning', 'afternoon'] for arrivals before 6pm"
},
"outboundArrivalTimeRange": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeRange",
"description": "Granular outbound arrival time range in minutes from midnight. Use this for precise time filtering. Cannot be used with outboundArrivalTimeBlocks."
},
"inboundDepartureTimeRange": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeRange",
"description": "Granular return departure time range in minutes from midnight for ROUND-TRIP searches. Cannot be used with inboundDepartureTimeBlocks."
},
"inboundTotalDurationRange": {
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Maximum duration in minutes"
},
"min": {
"type": "number",
"description": "Minimum duration in minutes"
}
},
"description": "Return flight duration filter (e.g., 'under 5 hours' = {max: 300}). Minutes. Round-trip only.",
"additionalProperties": false
},
"outboundArrivalTimeBlocks": {
"type": "array",
"items": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeBlocks/items"
},
"description": "Filter outbound arrival times. Use this to specify when you want to arrive at your destination. e.g. ['morning', 'afternoon'] for arrivals before 6pm"
},
"inboundDepartureTimeBlocks": {
"type": "array",
"items": {
"$ref": "#/properties/filters/properties/outboundDepartureTimeBlocks/items"
},
"description": "Filter return flight departure times for ROUND-TRIP searches. Use this to specify when you want the return leg to depart. e.g. ['morning', 'afternoon'] for departures before 6pm"
},
"outboundDepartureTimeRange": {
"type": "object",
"required": [
"min",
"max"
],
"properties": {
"max": {
"type": "integer",
"maximum": 1440,
"minimum": 0,
"description": "End time in minutes from midnight (0-1440). Example: 780 = 1:00 PM. Supports max=1440 for end-of-day (midnight). For midnight wraparound (e.g., 11pm-1am), max can be less than min."
},
"min": {
"type": "integer",
"maximum": 1439,
"minimum": 0,
"description": "Start time in minutes from midnight (0-1439). Example: 480 = 8:00 AM"
}
},
"description": "Granular outbound departure time range in minutes from midnight. Use this for precise time filtering (e.g., {min: 480, max: 780} for 8:00 AM - 1:00 PM). Cannot be used with outboundDepartureTimeBlocks.",
"additionalProperties": false
},
"outboundTotalDurationRange": {
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Maximum duration in minutes"
},
"min": {
"type": "number",
"description": "Minimum duration in minutes"
}
},
"description": "Outbound flight duration filter (e.g., 'under 3 hours' = {max: 180}). Minutes.",
"additionalProperties": false
},
"outboundDepartureTimeBlocks": {
"type": "array",
"items": {
"enum": [
"midnight",
"morning",
"afternoon",
"night"
],
"type": "string"
},
"description": "Filter outbound departure times. Use this to specify when you want to depart on the outgoing flight. e.g. ['morning', 'afternoon'] for departures before 6pm"
}
},
"description": "Flight filters to apply. When used with searchId (refinement), filters completely replace the previous filters. To preserve existing filters like airlines or departure times, include them again along with any new filters.",
"additionalProperties": false
},
"sorting": {
"enum": [
"score_desc",
"price_asc",
"duration_asc",
"leg1_departure_time_asc",
"leg1_departure_time_desc",
"leg2_departure_time_asc",
"leg2_departure_time_desc"
],
"type": "string",
"default": "score_desc",
"description": "Sort order for results. Pass a single string value. Options: score_desc (recommended, default), price_asc (cheapest), duration_asc (fastest), leg1_departure_time_asc/desc (outbound departure), leg2_departure_time_asc/desc (return departure, round-trip only)."
},
"pageSize": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1,
"description": "Trips per page on a searchId read (default 20, max 50). Out-of-range or non-integer values are rejected, never clamped."
},
"searchId": {
"type": "string",
"description": "Reuse the searchId from a previous search when refining, filtering, sorting, or selecting."
},
"siteCode": {
"type": "string",
"pattern": "^(?:[A-Z]{2})?$",
"description": "The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come from. Do NOT take it from the departure, arrival or hotel city: a user in India searching London is still 'IN'. Omit it when unknown (default 'US'). Set it when the search is created; a searchId read keeps the search's site."
},
"newSearch": {
"type": "object",
"required": [
"from",
"to",
"fromDate"
],
"properties": {
"to": {
"type": "string",
"minLength": 1,
"description": "Arrival IATA code (required for a new search when searchId is omitted)."
},
"from": {
"type": "string",
"minLength": 1,
"description": "Departure IATA code (required for a new search when searchId is omitted)."
},
"toDate": {
"type": "string",
"description": "Return date in YYYY-MM-DD for round-trip searches. Omit entirely for one-way trips (do not send null or empty string)."
},
"fromDate": {
"type": "string",
"minLength": 1,
"description": "Departure date in YYYY-MM-DD (required for a new search when searchId is omitted)."
},
"cabinClass": {
"enum": [
"economy",
"premium_economy",
"business",
"first"
],
"type": "string",
"default": "economy",
"description": "Requested cabin class for the search"
},
"adultsCount": {
"type": "number",
"default": 1,
"maximum": 9,
"minimum": 1,
"description": "Number of adult passengers (18+). Default: 1. Example: 'my wife and I' = 2 adults"
},
"infantsCount": {
"type": "number",
"default": 0,
"maximum": 8,
"minimum": 0,
"description": "Number of infant passengers (under 2 years). Default: 0. Typically on parent's lap"
},
"childrenCount": {
"type": "number",
"default": 0,
"maximum": 8,
"minimum": 0,
"description": "Number of child passengers (2-17). Default: 0. Example: 'with my 5-year-old' = 1 child"
}
},
"description": "Parameters required to create a new flight search when searchId is not provided. Include route (from/to), travel dates (fromDate/toDate in YYYY-MM-DD), and passenger counts. Use this to start a new Wego metasearch; omit when refining/polling an existing search via searchId.",
"additionalProperties": false
},
"currencyCode": {
"type": "string",
"description": "The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Discovers cheapest flight destinations from an origin city when the user has no specific destination in mind. Use for open-ended queries like 'where should I go?', 'cheapest flights from Dubai', 'surprise me', or 'best deals from Singapore'. Returns up to 15 cheapest destinations with prices, airlines, and travel dates. Do NOT use when user has a specific destination — use flights_search instead. Use IATA city codes from places_find_location.
The description explains the capability, when to use it, and what to expect.
Inputs88/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
origin
Departure city IATA code (e.g., DXB, SIN, LON)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
tripType
Trip type: 'roundtrip' (default) or 'oneway'
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
departureDate
Departure date (YYYY-MM-DD). Optional; API picks best dates if omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
returnDate
Return date (YYYY-MM-DD). Optional; ignored for oneway trips.
Clear enough to supply this argument.
locale
Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar').
Clear enough to supply this argument.
currencyCode
The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "flights_search_anywhere",
"title": "Search Flights Anywhere",
"description": "Discovers cheapest flight destinations from an origin city when the user has no specific destination in mind. Use for open-ended queries like 'where should I go?', 'cheapest flights from Dubai', 'surprise me', or 'best deals from Singapore'. Returns up to 15 cheapest destinations with prices, airlines, and travel dates. Do NOT use when user has a specific destination — use flights_search instead. Use IATA city codes from places_find_location.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"origin",
"currencyCode"
],
"properties": {
"locale": {
"type": "string",
"description": "Locale for results (e.g., 'en', 'ar', 'zh'). If not provided, uses the locale from the user's settings. Supports BCP 47 format (e.g., 'ar-SA' resolves to 'ar')."
},
"origin": {
"type": "string",
"pattern": "^[A-Z]{3}$",
"description": "Departure city IATA code (e.g., DXB, SIN, LON)"
},
"tripType": {
"enum": [
"roundtrip",
"oneway"
],
"type": "string",
"default": "roundtrip",
"description": "Trip type: 'roundtrip' (default) or 'oneway'"
},
"returnDate": {
"$ref": "#/properties/departureDate",
"description": "Return date (YYYY-MM-DD). Optional; ignored for oneway trips."
},
"currencyCode": {
"type": "string",
"description": "The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included."
},
"departureDate": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Departure date (YYYY-MM-DD). Optional; API picks best dates if omitted."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Finds the nearest airport to given coordinates. Returns airport IATA code, name, and distance. Useful for determining departure airport when only coordinates are known.
The description explains the capability, when to use it, and what to expect.
Inputs81/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
latitude
Latitude coordinate
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
longitude
Longitude coordinate
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "holidays_lookup",
"title": "Lookup Holidays",
"description": "Looks up public holidays for a country within a date range. Used for travel planning to find local holidays at the destination.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"country_code",
"start_date",
"end_date"
],
"properties": {
"locale": {
"type": "string",
"description": "Locale for localized holiday names (e.g., 'en', 'ar'). Defaults to 'en'."
},
"end_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "End date for the holiday search range in YYYY-MM-DD format. The range covers at most 366 days."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date for the holiday search range in YYYY-MM-DD format"
},
"country_code": {
"type": "string",
"pattern": "^[A-Za-z]{2}$",
"description": "ISO 3166-1 alpha-2 country code (e.g., 'SG', 'JP', 'US', 'TH')"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description85/100
Gets photos for one or more hotels (up to 8), up to 3 per category: rooms, bathrooms, dining, amenities such as the pool and gym, public spaces such as the lobby, exterior, views and nearby attractions. Hotels with no categories get up to 12 photos with no category. Use this tool for room photos too, because hotels_get_rooms gives only one image per room type. Use categoryFocus to show some categories first. missingHotelIds lists the hotels that could not be loaded.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
hotelIds
Array of hotel IDs to fetch photos for (1-8 hotels)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
categoryFocus
Photo categories to show first (does not filter). Pool and gym photos are in Amenities, lobby photos are in Public Spaces. Categories: Rooms, Bathrooms, Dining, Amenities, Public Spaces, Exterior, Views, Nearby Attractions, Others.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale for the hotel name (e.g., 'en', 'ar'). Category names and photo descriptions are always English.
Explain what happens when this optional value is omitted.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "hotels_get_photos",
"title": "Get Hotel Photos",
"description": "Gets photos for one or more hotels (up to 8), up to 3 per category: rooms, bathrooms, dining, amenities such as the pool and gym, public spaces such as the lobby, exterior, views and nearby attractions. Hotels with no categories get up to 12 photos with no category. Use this tool for room photos too, because hotels_get_rooms gives only one image per room type. Use categoryFocus to show some categories first. missingHotelIds lists the hotels that could not be loaded.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotelIds"
],
"properties": {
"locale": {
"type": "string",
"description": "Locale for the hotel name (e.g., 'en', 'ar'). Category names and photo descriptions are always English."
},
"hotelIds": {
"type": "array",
"items": {
"type": "integer",
"exclusiveMinimum": 0
},
"maxItems": 8,
"minItems": 1,
"description": "Array of hotel IDs to fetch photos for (1-8 hotels)"
},
"categoryFocus": {
"type": "array",
"items": {
"enum": [
"Rooms",
"Bathrooms",
"Dining",
"Amenities",
"Public Spaces",
"Exterior",
"Views",
"Nearby Attractions",
"Others"
],
"type": "string"
},
"description": "Photo categories to show first (does not filter). Pool and gym photos are in Amenities, lobby photos are in Public Spaces. Categories: Rooms, Bathrooms, Dining, Amenities, Public Spaces, Exterior, Views, Nearby Attractions, Others."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description88/100
Gets room rates for a specific hotel. Returns room types with pricing from multiple providers. Each rate's perNight price covers all rooms in the search together, for one night. Requires hotelId and searchId from a prior hotels_search call. If status is "incomplete", more rates are still loading: wait pollAgainInSeconds and call once more with the same arguments.
The description explains the capability, when to use it, and what to expect.
Inputs79/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
hotelId
Hotel ID from a previous hotels_search result
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
searchId
Search ID from a previous hotels_search result
Clear enough to supply this argument.
currencyCode
The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included.
Clear enough to supply this argument.
page
Page number (default: 1)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
perPage
Room types per page, 1-10 (default: 10)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale for results (default: 'en')
Explain the meaning of this value, not just its name.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "hotels_get_rooms",
"title": "Get Hotel Rooms",
"description": "Gets room rates for a specific hotel. Returns room types with pricing from multiple providers. Each rate's perNight price covers all rooms in the search together, for one night. Requires hotelId and searchId from a prior hotels_search call. If status is \"incomplete\", more rates are still loading: wait pollAgainInSeconds and call once more with the same arguments.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotelId",
"searchId",
"currencyCode"
],
"properties": {
"page": {
"type": "integer",
"minimum": 1,
"description": "Page number (default: 1)"
},
"locale": {
"type": "string",
"description": "Locale for results (default: 'en')"
},
"hotelId": {
"type": "integer",
"description": "Hotel ID from a previous hotels_search result",
"exclusiveMinimum": 0
},
"perPage": {
"type": "integer",
"maximum": 10,
"minimum": 1,
"description": "Room types per page, 1-10 (default: 10)"
},
"searchId": {
"type": "string",
"description": "Search ID from a previous hotels_search result"
},
"currencyCode": {
"type": "string",
"description": "The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Searches for hotel accommodations by city, geo-location, or hotel ID. Not for restaurants, activities, car rentals, or non-travel queries. Use places_find_location first to get codes/IDs/coordinates.
Each hotel price is per night for all rooms in the search together. With 2 rooms, a price covers both rooms.
Polling flow:
1. First call with search params (no searchId) → creates search session, returns searchId immediately (status: "created", pollAgainInSeconds: 5).
2. Wait pollAgainInSeconds, then call again with searchId → returns hotel results with status "incomplete" (better rates still arriving, pollAgainInSeconds says when to call again) or "complete" (all providers have answered).
3. While status is "incomplete", wait pollAgainInSeconds and call again. Stop when status is "complete". If it is still "incomplete" after 3 reads, use the results you have.
Once a search is complete, every read (new filters, sorting or pagination) returns status "complete" at once.
Search types (one per new search):
1. citySearch — Hotels in a city. Suitable for generic proximity queries (e.g., "near airports" or "downtown") when combined with sorting.
2. geoSearch — Hotels near a specific named location. Suitable when the user specifies a particular airport, landmark, or POI. Recommended radius: 10km for landmarks, 20km for airports.
3. hotelSearch — Single hotel by ID.
Proximity guidance:
- Generic proximity (e.g., "hotels near airport") → citySearch + "distance_from_nearest_airport_asc" sorting
- Generic city center (e.g., "downtown hotels") → citySearch + "distance_from_center_asc" sorting
- Named location (e.g., "hotels near Changi Airport") → geoSearch with POI coordinates + "distance_asc" sorting
- Explicit radius (e.g., "hotels within 15km of Eiffel Tower") → geoSearch with POI coordinates and radius
Integration with places_find_location:
- citySearch: get cityCode with types=["city"]
- geoSearch: get coordinates with types=["poi"]
Examples:
New search: { citySearch: { cityCode: "DXB" }, checkIn: "2025-11-06", checkOut: "2025-11-07", rooms: [{ adultsCount: 2, childrenCount: 0 }], sorting: "price_asc", currencyCode: "USD" }
Refinement: { searchId: "abc123", filters: { starRating: { min: 4 } }, sorting: "price_asc", currencyCode: "USD" }
Refinement: Provide the searchId from a previous response with updated filters, sorting, or pagination. Refinement replaces all previous filters — re-include existing ones to keep them.
Sorting (string): "relevance" (default), "price_asc", "price_desc", "star_rating_asc", "star_rating_desc", "review_score_asc", "review_score_desc", "distance_asc", "distance_from_center_asc", "distance_from_nearest_airport_asc"
Filters (flat object):
- amenities: hotel property amenities (wifi, pool, parking, gym, etc.)
- roomAmenities: room-level features (bathtub, balcony, minibar, free cancellation)
- starRating: { min?, max? } — star rating range (0-5)
- reviewScore: { min?, max? } — guest review score (0-10)
- priceRange: { min?, max? } — price per night for all rooms together (multiply a per-room budget by the number of rooms)
- propertyTypes: accommodation type (Hotel, Resort, Apartment, etc.)
- brands: hotel brand names (Holiday Inn, Hampton, etc.)
- chains: parent chains (Marriott, IHG, Hilton, etc.)
The description explains the capability, when to use it, and what to expect.
Inputs82/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
searchId
Reuse the searchId from a previous search when refining filters or sorting.
Clear enough to supply this argument.
citySearch › cityCode
City code (IATA format, e.g., 'DXB', 'SIN')
Clear enough to supply this argument.
geoSearch › longitude
Longitude coordinate (will be clamped to -180 to 180 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
geoSearch › latitude
Latitude coordinate (will be clamped to -90 to 90 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
geoSearch › radius
Search radius in kilometers (minimum 10km enforced). Recommended values: 10km for city landmarks, 20km for airports, 30km for rural areas
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
geoSearch › name
Name of the reference point for display (e.g., 'Burj Khalifa', 'Mall of the Emirates')
Explain the meaning of this value, not just its name.
hotelSearch › hotelId
Hotel ID for single hotel search
Clear enough to supply this argument.
checkIn
Check-in date in YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
checkOut
Check-out date in YYYY-MM-DD.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
rooms › items › adultsCount
Number of adults in the room (will be clamped to minimum 1)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
rooms › items › childrenCount
Number of children in the room (will be clamped to minimum 0)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
rooms › items › childrenAges
Ages of each child (0-17). REQUIRED when childrenCount > 0 — if the user hasn't specified ages, ask them before searching. Do NOT guess or infer ages from other numbers like dates. Array format even for one child, e.g., [8] not 8.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
siteCode
The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come from. Do NOT take it from the departure, arrival or hotel city: a user in India searching London is still 'IN'. Omit it when unknown (default 'US'). Set it when the search is created; a searchId read keeps the search's site.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › amenities
Hotel property amenities — all must match (AND logic). Covers wifi, pool, parking, gym, spa, beach, restaurant, pet-friendly, etc. Short terms match best (e.g., 'wifi' not 'Free WiFi', 'pool' not 'Swimming Pool'). Fuzzy matching finds the closest match.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › starRating › min
Minimum star rating (will be clamped to 0-5 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › starRating › max
Maximum star rating (will be clamped to 0-5 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › reviewScore › min
Minimum guest review score (will be clamped to 0-10 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › reviewScore › max
Maximum guest review score (will be clamped to 0-10 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › propertyTypes
Accommodation type filter (e.g., 'resorts only' = ['Resort'], 'hotel or apartment' = ['Hotel', 'Apartment']). Short terms match best.
Clear enough to supply this argument.
filters › priceRange › min
Minimum price per night for all rooms together. A negative value becomes 0.
Clear enough to supply this argument.
filters › priceRange › max
Maximum price per night for all rooms together. A negative value becomes 0.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › roomAmenities
Room-level amenities — all must match (AND logic). Covers room-specific features like 'bathtub', 'balcony', 'minibar', 'kitchen', 'free cancellation'. NOT for property-wide facilities (wifi, pool, gym) — those go in amenities.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
filters › brands
Hotel brand names (OR logic). Short names match best (e.g., 'Holiday Inn' not 'Holiday Inn Express by IHG'). Fuzzy matching finds the closest match.
Clear enough to supply this argument.
filters › chains
Parent hotel chains/groups (OR logic). Short names match best (e.g., 'Marriott' not 'Marriott - Marriott Rewards'). When user says 'Hilton hotels', use chains, not brands.
Clear enough to supply this argument.
sorting
Sort order (e.g., 'cheapest first' = 'price_asc', 'closest to center' = 'distance_from_center_asc'). Default: relevance.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
pagination › page
Page number for pagination (will be clamped to minimum 1)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
pagination › perPage
Number of results per page (will be clamped to 1-100 range)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale code (e.g., 'en', 'ar'). Default: 'en'.
Clear enough to supply this argument.
currencyCode
The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "hotels_search",
"title": "Search Hotels",
"description": "Searches for hotel accommodations by city, geo-location, or hotel ID. Not for restaurants, activities, car rentals, or non-travel queries. Use places_find_location first to get codes/IDs/coordinates.\n\nEach hotel price is per night for all rooms in the search together. With 2 rooms, a price covers both rooms.\n\nPolling flow:\n1. First call with search params (no searchId) → creates search session, returns searchId immediately (status: \"created\", pollAgainInSeconds: 5).\n2. Wait pollAgainInSeconds, then call again with searchId → returns hotel results with status \"incomplete\" (better rates still arriving, pollAgainInSeconds says when to call again) or \"complete\" (all providers have answered).\n3. While status is \"incomplete\", wait pollAgainInSeconds and call again. Stop when status is \"complete\". If it is still \"incomplete\" after 3 reads, use the results you have.\n\nOnce a search is complete, every read (new filters, sorting or pagination) returns status \"complete\" at once.\n\nSearch types (one per new search):\n1. citySearch — Hotels in a city. Suitable for generic proximity queries (e.g., \"near airports\" or \"downtown\") when combined with sorting.\n2. geoSearch — Hotels near a specific named location. Suitable when the user specifies a particular airport, landmark, or POI. Recommended radius: 10km for landmarks, 20km for airports.\n3. hotelSearch — Single hotel by ID.\n\nProximity guidance:\n- Generic proximity (e.g., \"hotels near airport\") → citySearch + \"distance_from_nearest_airport_asc\" sorting\n- Generic city center (e.g., \"downtown hotels\") → citySearch + \"distance_from_center_asc\" sorting\n- Named location (e.g., \"hotels near Changi Airport\") → geoSearch with POI coordinates + \"distance_asc\" sorting\n- Explicit radius (e.g., \"hotels within 15km of Eiffel Tower\") → geoSearch with POI coordinates and radius\n\nIntegration with places_find_location:\n- citySearch: get cityCode with types=[\"city\"]\n- geoSearch: get coordinates with types=[\"poi\"]\n\nExamples:\nNew search: { citySearch: { cityCode: \"DXB\" }, checkIn: \"2025-11-06\", checkOut: \"2025-11-07\", rooms: [{ adultsCount: 2, childrenCount: 0 }], sorting: \"price_asc\", currencyCode: \"USD\" }\nRefinement: { searchId: \"abc123\", filters: { starRating: { min: 4 } }, sorting: \"price_asc\", currencyCode: \"USD\" }\n\nRefinement: Provide the searchId from a previous response with updated filters, sorting, or pagination. Refinement replaces all previous filters — re-include existing ones to keep them.\n\nSorting (string): \"relevance\" (default), \"price_asc\", \"price_desc\", \"star_rating_asc\", \"star_rating_desc\", \"review_score_asc\", \"review_score_desc\", \"distance_asc\", \"distance_from_center_asc\", \"distance_from_nearest_airport_asc\"\n\nFilters (flat object):\n- amenities: hotel property amenities (wifi, pool, parking, gym, etc.)\n- roomAmenities: room-level features (bathtub, balcony, minibar, free cancellation)\n- starRating: { min?, max? } — star rating range (0-5)\n- reviewScore: { min?, max? } — guest review score (0-10)\n- priceRange: { min?, max? } — price per night for all rooms together (multiply a per-room budget by the number of rooms)\n- propertyTypes: accommodation type (Hotel, Resort, Apartment, etc.)\n- brands: hotel brand names (Holiday Inn, Hampton, etc.)\n- chains: parent chains (Marriott, IHG, Hilton, etc.)",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"currencyCode"
],
"properties": {
"rooms": {
"type": "array",
"items": {
"type": "object",
"required": [
"adultsCount",
"childrenCount"
],
"properties": {
"adultsCount": {
"type": "integer",
"description": "Number of adults in the room (will be clamped to minimum 1)"
},
"childrenAges": {
"type": "array",
"items": {
"type": "integer"
},
"description": "Ages of each child (0-17). REQUIRED when childrenCount > 0 — if the user hasn't specified ages, ask them before searching. Do NOT guess or infer ages from other numbers like dates. Array format even for one child, e.g., [8] not 8."
},
"childrenCount": {
"type": "integer",
"description": "Number of children in the room (will be clamped to minimum 0)"
}
},
"additionalProperties": false
},
"minItems": 1,
"description": "Room config (e.g., [{adultsCount: 2, childrenCount: 1, childrenAges: [8]}]). REQUIRED when childrenCount > 0: ask for ages before searching."
},
"locale": {
"type": "string",
"description": "Locale code (e.g., 'en', 'ar'). Default: 'en'."
},
"checkIn": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Check-in date in YYYY-MM-DD."
},
"filters": {
"type": "object",
"properties": {
"brands": {
"type": "array",
"items": {
"type": "string"
},
"description": "Hotel brand names (OR logic). Short names match best (e.g., 'Holiday Inn' not 'Holiday Inn Express by IHG'). Fuzzy matching finds the closest match."
},
"chains": {
"type": "array",
"items": {
"type": "string"
},
"description": "Parent hotel chains/groups (OR logic). Short names match best (e.g., 'Marriott' not 'Marriott - Marriott Rewards'). When user says 'Hilton hotels', use chains, not brands."
},
"amenities": {
"type": "array",
"items": {
"type": "string"
},
"description": "Hotel property amenities — all must match (AND logic). Covers wifi, pool, parking, gym, spa, beach, restaurant, pet-friendly, etc. Short terms match best (e.g., 'wifi' not 'Free WiFi', 'pool' not 'Swimming Pool'). Fuzzy matching finds the closest match."
},
"priceRange": {
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Maximum price per night for all rooms together. A negative value becomes 0."
},
"min": {
"type": "number",
"description": "Minimum price per night for all rooms together. A negative value becomes 0."
}
},
"description": "Budget filter on the price per night for all rooms together, in currencyCode. To filter on a per-room budget, multiply it by the number of rooms. For a total-stay budget, divide it by the number of nights. Examples: '2 rooms, under USD 50 for each room per night' = {max: 100}. 'USD 600 for 3 nights, 2 rooms' = {max: 200}.",
"additionalProperties": false
},
"starRating": {
"type": "object",
"properties": {
"max": {
"type": "integer",
"description": "Maximum star rating (will be clamped to 0-5 range)"
},
"min": {
"type": "integer",
"description": "Minimum star rating (will be clamped to 0-5 range)"
}
},
"description": "Hotel class filter (e.g., '4-star or above' = {min: 4}, '3 to 4 stars' = {min: 3, max: 4}).",
"additionalProperties": false
},
"reviewScore": {
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Maximum guest review score (will be clamped to 0-10 range)"
},
"min": {
"type": "number",
"description": "Minimum guest review score (will be clamped to 0-10 range)"
}
},
"description": "Guest satisfaction filter on 0-10 scale (e.g., 'highly rated' = {min: 8}).",
"additionalProperties": false
},
"propertyTypes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Accommodation type filter (e.g., 'resorts only' = ['Resort'], 'hotel or apartment' = ['Hotel', 'Apartment']). Short terms match best."
},
"roomAmenities": {
"type": "array",
"items": {
"type": "string"
},
"description": "Room-level amenities — all must match (AND logic). Covers room-specific features like 'bathtub', 'balcony', 'minibar', 'kitchen', 'free cancellation'. NOT for property-wide facilities (wifi, pool, gym) — those go in amenities."
}
},
"description": "Filters to apply to search results.",
"additionalProperties": false
},
"sorting": {
"enum": [
"relevance",
"price_asc",
"price_desc",
"star_rating_asc",
"star_rating_desc",
"review_score_asc",
"review_score_desc",
"distance_asc",
"distance_from_center_asc",
"distance_from_nearest_airport_asc"
],
"type": "string",
"default": "relevance",
"description": "Sort order (e.g., 'cheapest first' = 'price_asc', 'closest to center' = 'distance_from_center_asc'). Default: relevance."
},
"checkOut": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Check-out date in YYYY-MM-DD."
},
"searchId": {
"type": "string",
"description": "Reuse the searchId from a previous search when refining filters or sorting."
},
"siteCode": {
"type": "string",
"pattern": "^(?:[A-Z]{2})?$",
"description": "The user's OWN country as an ISO 3166-1 alpha-2 code (e.g. 'SG', 'SA', 'IN'), when the conversation shows where the user is. It picks the Wego site that booking links open and the market prices come from. Do NOT take it from the departure, arrival or hotel city: a user in India searching London is still 'IN'. Omit it when unknown (default 'US'). Set it when the search is created; a searchId read keeps the search's site."
},
"geoSearch": {
"type": "object",
"required": [
"longitude",
"latitude"
],
"properties": {
"name": {
"type": "string",
"description": "Name of the reference point for display (e.g., 'Burj Khalifa', 'Mall of the Emirates')"
},
"radius": {
"type": "number",
"description": "Search radius in kilometers (minimum 10km enforced). Recommended values: 10km for city landmarks, 20km for airports, 30km for rural areas"
},
"latitude": {
"type": "number",
"description": "Latitude coordinate (will be clamped to -90 to 90 range)"
},
"longitude": {
"type": "number",
"description": "Longitude coordinate (will be clamped to -180 to 180 range)"
}
},
"description": "Hotels near a location (e.g., 'near Eiffel Tower' = {latitude: 48.8584, longitude: 2.2945}). Use places_find_location for coordinates.",
"additionalProperties": false
},
"citySearch": {
"type": "object",
"required": [
"cityCode"
],
"properties": {
"cityCode": {
"type": "string",
"description": "City code (IATA format, e.g., 'DXB', 'SIN')"
}
},
"description": "Hotels in a city (e.g., 'hotels in Dubai' = {cityCode: 'DXB'}).",
"additionalProperties": false
},
"pagination": {
"type": "object",
"default": {
"page": 1,
"perPage": 8
},
"properties": {
"page": {
"type": "integer",
"default": 1,
"description": "Page number for pagination (will be clamped to minimum 1)"
},
"perPage": {
"type": "integer",
"default": 8,
"description": "Number of results per page (will be clamped to 1-100 range)"
}
},
"description": "Pagination settings",
"additionalProperties": false
},
"hotelSearch": {
"type": "object",
"required": [
"hotelId"
],
"properties": {
"hotelId": {
"type": "integer",
"description": "Hotel ID for single hotel search"
}
},
"description": "Single hotel by ID (e.g., {hotelId: 12345}).",
"additionalProperties": false
},
"currencyCode": {
"type": "string",
"description": "The currency the user pays in, as an ISO 4217 code (e.g. 'SAR', 'INR', 'USD'): the one they ask for, else the currency of their own country (siteCode). Do NOT take it from the destination: a user in India booking Dubai pays in 'INR'. Send the same code on every flight and hotel call in this conversation, searchId reads included."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Search for cities, airports, districts, states, hotels, or points of interest by name. Returns location codes, IDs, and coordinates. Supports pagination (default: 10 results per page).
PLACE TYPES:
Filter by specific types using the 'types' parameter:
- city: Major cities (returns cityCode like "DXB", "PAR")
- airport: Airports (returns IATA codes like "JFK", "LHR")
- district: Neighborhoods within cities (returns districtId)
- state: States, provinces, regions
- hotel: Individual hotels (returns hotelId)
- poi: Points of interest, landmarks (returns coordinates)
If 'types' is omitted, returns all matching place types.
POI SEARCH WITH LOCATION BIAS:
POI search uses Google Places API. You can optionally provide locationBias (approximate coordinates) to improve result relevance when geographic context is known.
When to provide locationBias:
- User mentions a city: "Eiffel Tower in Paris" (provide Paris coordinates)
- Previous conversation context provides location
- You recognize the landmark location
When NOT to provide locationBias:
- No geographic context available
- Uncertain about location
- Global/ambiguous landmarks
EXAMPLES:
Find city: { query: "Dubai" } returns cityCode: "DXB"
Find district: { query: "Downtown Dubai", types: ["district"] } returns districtId
Find airports: { query: "New York", types: ["airport"] } returns JFK, LGA, EWR
Find hotel: { query: "Burj Al Arab", types: ["hotel"] } returns hotelId
Find POI with bias: { query: "Eiffel Tower", types: ["poi"], locationBias: { latitude: 48.85, longitude: 2.35 } }
Find POI without bias: { query: "Marina Bay Sands", types: ["poi"] }
Pagination: { query: "hotel", pageSize: 10, page: 2 } returns results 11-20
AMBIGUITY HANDLING:
When multiple locations match, response includes hasAmbiguity: true and disambiguationHint. Ask user to specify which location.
NOTES:
- locationBias is optional (text search works without it)
- Approximate coordinates are fine (city-level accuracy)
- Location bias improves relevance but doesn't exclude other regions
The description explains the capability, when to use it, and what to expect.
Inputs71/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Search query for the location
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
types
Array of place types to filter results. If omitted, returns all types.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locationBias › latitude
Latitude for location bias (helps narrow POI search results)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locationBias › longitude
Longitude for location bias (helps narrow POI search results)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
locale
Locale code for localized results (falls back to user's locale from platform metadata)
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
page
Page number for pagination (default: 1)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
pageSize
Number of results per page (default: 10, max: 50)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "places_find_location",
"title": "Find Location",
"description": "Search for cities, airports, districts, states, hotels, or points of interest by name. Returns location codes, IDs, and coordinates. Supports pagination (default: 10 results per page).\n\nPLACE TYPES:\nFilter by specific types using the 'types' parameter:\n- city: Major cities (returns cityCode like \"DXB\", \"PAR\")\n- airport: Airports (returns IATA codes like \"JFK\", \"LHR\")\n- district: Neighborhoods within cities (returns districtId)\n- state: States, provinces, regions\n- hotel: Individual hotels (returns hotelId)\n- poi: Points of interest, landmarks (returns coordinates)\n\nIf 'types' is omitted, returns all matching place types.\n\nPOI SEARCH WITH LOCATION BIAS:\nPOI search uses Google Places API. You can optionally provide locationBias (approximate coordinates) to improve result relevance when geographic context is known.\n\nWhen to provide locationBias:\n- User mentions a city: \"Eiffel Tower in Paris\" (provide Paris coordinates)\n- Previous conversation context provides location\n- You recognize the landmark location\n\nWhen NOT to provide locationBias:\n- No geographic context available\n- Uncertain about location\n- Global/ambiguous landmarks\n\nEXAMPLES:\nFind city: { query: \"Dubai\" } returns cityCode: \"DXB\"\nFind district: { query: \"Downtown Dubai\", types: [\"district\"] } returns districtId\nFind airports: { query: \"New York\", types: [\"airport\"] } returns JFK, LGA, EWR\nFind hotel: { query: \"Burj Al Arab\", types: [\"hotel\"] } returns hotelId\nFind POI with bias: { query: \"Eiffel Tower\", types: [\"poi\"], locationBias: { latitude: 48.85, longitude: 2.35 } }\nFind POI without bias: { query: \"Marina Bay Sands\", types: [\"poi\"] }\nPagination: { query: \"hotel\", pageSize: 10, page: 2 } returns results 11-20\n\nAMBIGUITY HANDLING:\nWhen multiple locations match, response includes hasAmbiguity: true and disambiguationHint. Ask user to specify which location.\n\nNOTES:\n- locationBias is optional (text search works without it)\n- Approximate coordinates are fine (city-level accuracy)\n- Location bias improves relevance but doesn't exclude other regions",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"page": {
"type": "integer",
"default": 1,
"minimum": 1,
"description": "Page number for pagination (default: 1)"
},
"query": {
"type": "string",
"minLength": 1,
"description": "Search query for the location"
},
"types": {
"type": "array",
"items": {
"enum": [
"city",
"airport",
"state",
"district",
"hotel",
"poi"
],
"type": "string"
},
"description": "Array of place types to filter results. If omitted, returns all types."
},
"locale": {
"type": "string",
"description": "Locale code for localized results (falls back to user's locale from platform metadata)"
},
"pageSize": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1,
"description": "Number of results per page (default: 10, max: 50)"
},
"locationBias": {
"type": "object",
"required": [
"latitude",
"longitude"
],
"properties": {
"latitude": {
"type": "number",
"maximum": 90,
"minimum": -90,
"description": "Latitude for location bias (helps narrow POI search results)"
},
"longitude": {
"type": "number",
"maximum": 180,
"minimum": -180,
"description": "Longitude for location bias (helps narrow POI search results)"
}
},
"description": "Optional coordinates to bias POI search results. Useful when searching for landmarks in a specific region. The LLM can provide approximate city/region coordinates based on context.",
"additionalProperties": false
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}
Loading score analytics…
Put your MCP to the test
A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.
01Lookup HolidaysLooks up public holidays for a country within a date range.
02Find LocationSearch for cities, airports, districts, states, hotels, or points of interest by name.
03Flight One-Way PriceShows cheapest one-way flight prices across a date range.
04Flight ScheduleGets the current published timetable of nonstop flights between two cities: airlines, flight numbers, departure and arrival airports and times, duration, and…
05Search Flights AnywhereDiscovers cheapest flight destinations from an origin city when the user has no specific destination in mind.
Want to run these tasks against your MCP server with us?
Wego setup, tools, quality score, publishing readiness, and alternatives.
How do I add Wego to Claude, ChatGPT, or Cursor?
Add Wego to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.wego.com/public-app/v1/mcp.
Is Wego MCP ready for ChatGPT and Claude?
As of November 17, 2026, Wego scores 96/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is Wego's MCP tool documentation?
As of November 17, 2026, Wego scores 82/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 10 of 10 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to Wego?
As of November 17, 2026, alternatives to Wego in commerce-shopping on the Manufact MCP leaderboard include REMAX Europe, Product Hunt, Square Yards, eno.vn Partner API, and POD Benchmark.
How can Wego improve its MCP documentation?
holidays_lookup is the lowest-scoring reviewed tool at 78/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.