Submit a Trip Request (Consultant Handoff)
trip_idea_createSubmit the customer's trip to AirTreks as a complete, structured trip request - a human travel consultant takes over from there. Ask the traveler for everything before calling, never guess or fill in defaults: name, email, the cities in order (3-letter IATA codes), a departure date for every leg, number of passengers, cabin (economy, premium or business), and their answers to AirTreks' planning questions. Also ask about budget, flexible dates, preferences and anything else the consultant should know. Call once without questionsAnswers to receive the current planning questions to put to the traveler.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"email": "<email>",
"name": "<name>",
"cities": "<cities>",
"dates": "<dates>",
"passengers": "<passengers>",
"cabin": "<cabin>"
},
"name": "trip_idea_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Customer full name (required — the consultant contacts them by name) | |
| cabin | Yes | Cabin class (required — ask the customer, there is no default) | |
| dates | Yes | Departure dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. Ask the customer; never invent dates. If they only know roughly, use their stated estimates and set flexibleDates. | |
| Yes | Customer email address (required) | ||
| notes | No | Additional notes or special requests from the customer | |
| phone | No | Customer phone number | |
| budget | No | Budget tier | |
| cities | Yes | Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK']) | |
| source | No | The AI platform or app this conversation is running in, lowercase (e.g. 'chatgpt', 'claude', 'perplexity'). Only tells AirTreks which channel the request came through — never put customer details here. Omit it if you don't know. | |
| passengers | Yes | Number of passengers (required — ask the customer, there is no default) | |
| preferences | No | Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok' | |
| agentContext | No | Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.) | |
| sourceDetail | No | Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here. | |
| flexibleDates | No | Are travel dates flexible? | |
| questionsAnswers | No | The customer's answers to AirTreks' planning questions, keyed by question name (e.g. {"guidance": "I want expert guidance from humans"}). The answers must come from the customer — never pick one yourself. A JSON-encoded string of the same object is also accepted. Required, but don't guess the questions: call once without this — the response lists the current questions and their options to ask the customer. |