aitrips.io

trip_item_add

Add an item to a trip (accommodation, activity, flight, meal, transport)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date (YYYY-MM-DD)
`name`	Yes	Item name (e.g., "Shangri-La Hotel", "British Museum")
`type`	Yes	Type of item
`notes`	No	Additional notes
`status`	No	Item status. Canonical values: IDEA, SHORTLISTED, BOOKED, COMPLETED, CANCELLED. Legacy aliases accepted: RESEARCHED→SHORTLISTED, CONFIRMED→BOOKED.
`tripId`	Yes	Trip ID
`address`	No	Full address (more accurate geocoding)
`endDate`	No	End date for multi-day items like hotels (YYYY-MM-DD). Must be >= date. Use for accommodation check-out date, car rental return date, multi-day tours, etc.
`timeEnd`	No	End time (HH:MM)
`currency`	No	Currency code
`latitude`	No	Latitude (optional if address/location provided)
`location`	No	Location name (will be geocoded if no coordinates provided)
`priority`	No	Priority level	MEDIUM
`timezone`	No	IANA timezone for this item (e.g., "Europe/London", "America/New_York"). If not set, defaults to the trip timezone. Use when the item is in a different timezone than the trip (e.g., a flight departing from London on a Paris trip).
`longitude`	No	Longitude (optional if address/location provided)
`sortOrder`	No	Explicit sort position within the day. When omitted, smart placement is applied: timed items are inserted at the chronological position among existing timed items; untimed items and accommodation are appended at the end of the day.
`timeStart`	No	Start time (HH:MM)
`bookingUrl`	No	Booking URL
`description`	No	Detailed description
`costEstimate`	No	Estimated cost
`originAddress`	No	Departure address (FLIGHT/TRANSPORT only — prefer trip_transport_add for these types). Will be geocoded if no coordinates provided.
`originLatitude`	No	Departure latitude (FLIGHT/TRANSPORT only — prefer trip_transport_add)
`originLocation`	No	Departure location name (FLIGHT/TRANSPORT only — prefer trip_transport_add for these types). Will be geocoded automatically.
`costIsPerPerson`	No	Is cost per person?
`originLongitude`	No	Departure longitude (FLIGHT/TRANSPORT only — prefer trip_transport_add)
`bookingReference`	No	Booking reference number
`confirmationNumber`	No	Confirmation number

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 23, 2026

changedInput schema / properties / address / description

Previous value: -"Full address"New value: +"Full address (more accurate geocoding)"

addedInput schema / properties / bookingReference

Added value: +{
+  "description": "Booking reference number",
+  "type": "string"
+}

addedInput schema / properties / confirmationNumber

Added value: +{
+  "description": "Confirmation number",
+  "type": "string"
+}

changedInput schema / properties / latitude / description

Previous value: -"Latitude"New value: +"Latitude (optional if address/location provided)"

changedInput schema / properties / location / description

Previous value: -"Location name"New value: +"Location name (will be geocoded if no coordinates provided)"

changedInput schema / properties / longitude / description

Previous value: -"Longitude"New value: +"Longitude (optional if address/location provided)"

addedInput schema / properties / originAddress

Added value: +{
+  "description": "Departure address (FLIGHT/TRANSPORT only — prefer trip_transport_add for these types). Will be geocoded if no coordinates provided.",
+  "type": "string"
+}

addedInput schema / properties / originLatitude

Added value: +{
+  "description": "Departure latitude (FLIGHT/TRANSPORT only — prefer trip_transport_add)",
+  "type": "number"
+}

addedInput schema / properties / originLocation

Added value: +{
+  "description": "Departure location name (FLIGHT/TRANSPORT only — prefer trip_transport_add for these types). Will be geocoded automatically.",
+  "type": "string"
+}

addedInput schema / properties / originLongitude

Added value: +{
+  "description": "Departure longitude (FLIGHT/TRANSPORT only — prefer trip_transport_add)",
+  "type": "number"
+}

addedInput schema / properties / sortOrder

Added value: +{
+  "description": "Explicit sort position within the day. When omitted, smart placement is applied: timed items are inserted at the chronological position among existing timed items; untimed items and accommodation are appended at the end of the day.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone for this item (e.g., \"Europe/London\", \"America/New_York\"). If not set, defaults to the trip timezone. Use when the item is in a different timezone than the trip (e.g., a flight departing from London on a Paris trip).",
+  "type": "string"
+}

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / endDate

Added value: +{
+  "description": "End date for multi-day items like hotels (YYYY-MM-DD). Must be >= date. Use for accommodation check-out date, car rental return date, multi-day tours, etc.",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already communicate a non-destructive mutation (readOnlyHint=false, destructiveHint=false), and the description's 'Add' merely restates that operation without adding context. It does not disclose side effects such as geocoding, smart sort placement, timezone defaults, or what happens on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with no filler, and the parenthetical enumeration of item types is useful and front-loaded. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The rich schema and annotations make the tool invokable for basic use, but the overall definition is incomplete for a 27-parameter tool with no output schema: it lacks return behavior, prerequisites, failure semantics, and explicit routing to trip_transport_add for transport items. It is adequate, but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the parameter descriptions are unusually rich (status aliases, timezone defaults, sortOrder behavior, geocoding notes), so the schema carries the parameter-documentation burden. The top-level description adds no parameter meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete action and resource ('Add an item to a trip') and enumerates the accepted item types, so an agent can tell what the tool does at a glance. It is not quite a 5 because it does not differentiate this from trip_transport_add, which is the preferred sibling for FLIGHT/TRANSPORT items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance or exclusions, despite many nearby sibling tools such as trip_transport_add and trip_item_update. The schema's origin* parameter descriptions mention preferring trip_transport_add for FLIGHT/TRANSPORT, but the tool description itself does not guide the agent toward or away from alternatives.

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

All aitrips.io 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.

trip_item_add

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources