flight_tools_intro
ChatGPTOpen the flight search usage guide for finding flights, comparing airfares, and choosing the right flight tool. Returns the complete usage guide for these Trip.com-backed flight MCP tools: tool list, mandatory call order, parameter rules, and worked examples for common scenarios. Call this tool first if you are unsure which tool to use or how to construct a request.
search_flights
ChatGPTUse this when the user wants real-time flight options for fixed-date travel, including "cheapest flight on this date" requests. This tool searches Trip.com inventory. Relative dates such as tomorrow or next Thursday count as fixed-date travel after resolving them to YYYYMMDD. Supports one-way and round-trip itineraries only. For multi-way requests, offer to search each leg as a separate one-way trip. Each segment is one real flight leg in itinerary order, not one origin-destination pair generated from alternatives. oneWay uses exactly 1 segment. roundTrip uses exactly 2 segments using the same locations in reverse directions. For multiple possible departure or arrival places on the same leg/date, keep them in the same segment by passing multiple departLocations and/or arriveLocations. Do not create extra segments for location alternatives. For example, "Shanghai or Beijing to Tokyo on 2026-04-15" is one segment with two departLocations and one arriveLocation; "Shanghai to Tokyo or Osaka" is one segment with one departLocation and two arriveLocations. Preserve the exact location granularity the user requested: if the user says a country/region such as Japan or Australia, pass that country/region name directly. Do not replace or expand a country/region with representative or inferred cities such as Tokyo, Osaka, or Sydney unless the user explicitly chose those cities. Do not use this for flexible, approximate, or range-based date searches; use search_low_price_flights_v2 for flexible dates whether or not the user says "cheap". Each segment needs departLocations, arriveLocations, and departDate in YYYYMMDD. Departure and arrival locations may be human-readable city, country/region, or airport names; the server resolves flight location codes internally. Optional filters include airline codes, cabin class, baggage allowance, and student fares.
search_low_price_flights
ChatGPTSearch for available flights between cities. Supports one-way and round-trip flights. Use segments array: single element for one-way, two elements for round-trip.
search_low_price_flights
ChatGPTSearch for available flights between cities. Supports one-way and round-trip flights. Use segments array: single element for one-way, two elements for round-trip.
search_low_price_flights_v2
ChatGPTUse this when the user wants low-price flight options for flexible-date itineraries. This tool searches Trip.com inventory and returns fare options users can compare and continue to book. The travel date should be flexible, approximate, or a date range such as "next month", "Golden Week", or "any cheap day in June". Do not use this for a specific departure day; use search_flights even when the user asks for the cheapest flight on an exact date. If the user gives no date or date range, ask for an exact departure date or a flexible date window before calling. If the user mixes exact-date and flexible-date alternatives, ask whether to run exact search, flexible-date search, or both separately. For ambiguous named holidays such as Golden Week, ask which market, year, or holiday window the user means before calling. Supports one-way and round-trip searches only. For multi-way requests, offer to search each leg as a separate one-way trip. Each segment needs one origin.name, one destination.name, and departureTimeRange in YYYY-MM-DD. Only accepts tripType, rawQuery, locale, and segments; filters such as cabin class, airline, direct/nonstop flights, baggage, student fares, or transfer cities are not supported. Still use this for flexible-date queries with unsupported filters, but omit those filters and explain the limitation. For one-way, the departureTimeRange span must be within one month; for round-trip, the overall span from the earliest outbound departure to the latest return departure must be within one month. For wider flexible windows, stay in the flexible-date path and ask the user to narrow the window or split it into multiple search_low_price_flights_v2 searches.
search_train_routes
ChatGPTSearch train routes between two stations or cities. Returns departure/arrival times, prices when available, journey duration, transfer information, and route options. Supports sorting by price or duration, and filtering by transfer count (direct only = 0, max 1 transfer = 1, or unlimited = -1) and earliest departure time of day (HH:mm:ss). Date defaults to tomorrow if omitted.
