← Plugin catalog
Travel

Cruise Itinerary

BigBalli Consulting v1.0.6

Cruise schedules and fares

Create a free account to save this plugin.

From the developer

Declared limitations

  • A booking request the read-only tools cannot do
  • A per-day passenger count the data does not hold, where the port capacity tool looks relevant
  • A cruise line outside the coverage, where the search tool looks relevant

Not specified in the available declarations: capabilities, pricing & account requirements.

Onboarding example

Find Allure of the Seas sailings from Miami in January 2027, cheapest balcony first.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 13, 2026. Package observed Nov 13, 2026.

View package source →

Description

From the marketplace listing

Cruise Itinerary is a cruise finder and a weekly register of the cruise market, inside ChatGPT. Find cruises by ship, cruise line, port of call, departure port, region, dates, length, cabin and fare, then read each sailing's day-by-day itinerary. Behind every answer is real data: upcoming sailings across more than 40 cruise lines, the weekly fare history of any sailing, how much ship capacity reaches a port each month, and the Cruise Price Index, a weekly measure of how cruise fares are moving. It is built for people who need every line at once: shore-excursion and tour operators planning around ship calls, ports and destinations comparing their season, travel planners grounding itineraries in real sailings, and analysts and journalists tracking fares. Start with any name, however it is spelt: the resolver turns "Port Canaveral", "Symphony of the Seas" or "NCL" into the ids the other tools use. Every answer carries its caveats. Fares are weekly snapshots captured every Monday, not live or bookable prices, and a missing fare means the cabin was not offered or was sold out. Itinerary days are marked exact when they come from the cruise line's published itinerary and estimated when they were placed from the route. Port capacity is monthly and counts berths, which are capacity, not passengers. Coverage is strongest for North American lines; TUI Cruises/Marella, AIDA, Saga, Fred. Olsen and Hapag-Lloyd are not covered. Connecting uses your Cruise Itinerary account. Every tool is read-only.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 13, 2026. Last seen Nov 13, 2026.

Keywords

Files & skills

File archives

Plugin package6 files · 31.2 KBBrowse files →
Skill instructions
cruise-research5.77 KB

View saved version →

---
name: cruise-research
description: Research cruises with the Cruise Itinerary tools - find sailings, read day-by-day itineraries, track weekly fare changes, size port traffic by month and read the Cruise Price Index - and report the results with the data's caveats (weekly fares are not live, a missing fare means not offered or sold out, berths are capacity not passengers, port capacity is monthly only, estimated days can be off by one). Use whenever the user asks about cruise sailings, ships, ports of call, cruise fares or prices, itineraries, or cruise ship traffic at a port.
---

# Cruise research with Cruise Itinerary

The `cruise-itinerary` MCP server gives read-only access to a weekly register of cruise lines, ships, ports and upcoming sailings, kept by cruise-itinerary.com. This skill is about using it well and reporting what it says honestly.

## Work in this order

1. **Resolve names first.** Call `resolve_entity` with the name the user gave ("Port Canaveral", "Symphony of the Seas", "NCL"). Every other tool takes the returned `id` (a slug), never a free-text name. Pass `type` when you know it (`port`, `ship`, `line`).
   - Confidence 1.0 is an exact name. Below about 0.6 is a guess: show the candidates and ask the user which one they mean instead of picking one.
   - A port can have near-duplicates (for example `skagway` and `skagway-alaska-usa`). Prefer the exact match, and say so if results look split.
2. **Find sailings** with `search_sailings`: filter by `ship`, `line`, `port` (calls there), `embark_port`, `region`, departure `from`/`to`, `min_nights`/`max_nights`, `cabin`, `max_fare`. Use `sort: "fare"` for the cheapest first. Page with `page` and `per_page` (up to 50); `meta.total` says how many match.
3. **Open one sailing** with `get_itinerary` and its `sailing_id` for the dated day-by-day plan, or with `cruise_id` for the route shared by all sailings of that cruise.
4. **Fare history** for one sailing: `get_price_history` with the `sailing_id`.
5. **Port traffic**: `port_month_capacity` with a port `id`, a `from_month` (YYYY-MM) and `months` (up to 24).
6. **Market-wide price movement**: `cruise_price_index`. `view: "latest"` gives the last 12 weeks for all lines and the largest lines; `view: "series"` gives one line, cabin and segment over time.

## Report the caveats every time they apply

- **Fares are weekly snapshots, not live prices.** They are captured every Monday; `meta.as_of` is the date of the latest load. Say "as of <date>" and never present a fare as bookable or current. Send people to the cruise line or a travel agent to book.
- **A missing fare (null) means the cabin was not offered or was sold out** at capture time. The data does not say which. Do not call it "sold out" or "unavailable" on its own.
- **Fares are the lowest fare per cabin class, in whole US dollars**, as the supplier listed it. Do not add taxes or convert currencies unless asked, and say so if you do.
- **Itinerary days have a confidence.** `day_confidence: "exact"` comes from the cruise line's published itinerary (embark and disembark days are always exact). `"estimated"` days were placed from the distance between ports and can be off by a day. When you give a date for an estimated call, say it is estimated. On a cruise, `itinerary_source: "official"` means day numbers come from the line; `"supplier"` means only the order of stops is known.
- **Berths are capacity, not passengers.** `port_month_capacity` sums each ship's lower-berth capacity over every ship-day in port. Real passenger numbers differ (ships sail above or below lower-berth capacity). Write "berths" or "passenger capacity", never "passengers" or "visitors".
- **Port capacity is monthly only.** There are no per-day counts, by design: many call days are estimated. Do not divide a month into days or present a "busiest day" from this data. `ship_days` counts a ship in port two days twice; `distinct_ships` counts each ship once.
- **Coverage.** Strongest for North

Preview of the first 4,000 characters. Read full instructions →

Release notes

Initial release: find cruise sailings, read day-by-day itineraries, follow weekly fare history and monthly port capacity, and read the Cruise Price Index.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
BigBalli Consulting LLC
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 13, 2026.

Technical details
First seen
Nov 13, 2026 · 18:00 UTC
Last seen
Nov 13, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6ad6b2bbd07481918db7dc8a90f173b4

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.