faq_lookup
ChatGPTLook up Princess Cruises help content (policies, onboard info, trip planning) for passages relevant to a general question not tied to a specific cruise. For finding or filtering cruises, use
search instead.By Princess Cruise Lines, Ltd.
Ask anything in plain English and get instant answers pulled directly from Princess.com — destinations, itineraries, sail dates, and pricing. Explore the full Princess catalog without switching tabs, then go straight to booking when you're ready. What you can do: • Search by destination, date, duration, or departure port • Discover itineraries and ports matched to your interests • Jump directly to Princess.com to book Try asking: 1. Which Mediterranean itineraries sail in May? 2. What Caribbean ports does Princess visit in winter? 3. Show me Alaska cruises from Seattle
search instead.embedding column). Accepts a single string literal, e.g. embedding <=> embed('romantic'). Only the first 256 tokens are embedded. These tables carry an embedding column: excursion_reviews, excursions, lodges, places, ships, stateroom_categories, stateroom_subgroups. No other table has one. In particular products and voyages have none, so a whole trip has no vector of its own — match the mood on the ship, the ports it visits, or its excursions, and join back to the sailing. Express soft/semantic constraints in SQL with pgvector's cosine-distance operator <=>, always written as <table>.embedding, for example: ORDER BY ships.embedding <=> embed('romantic sunset dinner') LIMIT 20 WHERE (places.embedding <=> embed('glacier hike')) < 0.6 Treat the distance as a score — a bare embedding column can't be returned. PRODUCT KINDS: the catalog has two products.kind values — 'cruise' and 'cruisetour' (a cruise bundled with a land tour). A cruisetour is a cruise. When the user says "cruise" without singling out one kind, search both; add a kind filter only when they explicitly ask for one (e.g. "cruisetour packages", or "a cruise, not a land tour"). AVAILABILITY: only pricing.available says whether a sailing can still be booked — you MUST check it whenever you're picking sailings to recommend — including when the shopper mentioned no price or cabin. RESULTS: capped at ~500 KB of data, not a fixed row count — small rows pack more in. When more rows match than fit, truncated is true and the true match count is reported. Database date range: 2026-09-26 to 2028-11-18 TABLES (column comments carry units, joins, and valid values): ships — Princess ships. Join voyages.ship_code = ships.code. code text — 2-letter ship code, e.g. 'RP'. name text — Ship name, e.g. 'Royal Princess'. description text — Marketing prose about the ship. image_url text ship_version int spec jsonb — Label/value rows (guest capacity, crew, tonnage, …). stateroom_types text[] amenity_categories jsonb — Marketing groups (dining, entertainment) with items. zones jsonb — Deck zones (Forward/Midship/Aft). version_dates jsonb embedding vector(1024) — Vector of name, description, and dining/entertainment/amenity items. places — Everywhere a cruise stops. Whether a given stop is a port call or a land stop is a property of the stop, so read itinerary_days.stop_type for that, not this table. code text — 3-char place code, e.g. 'JNU'. name text — Full name, carrying the state or country, e.g. 'Juneau, Alaska'. is_port boolean — TRUE when the place is a port. A place can be both port and city at the same time — do NOT treat these as mutually exclusive. is_city boolean — TRUE when the place is a cruisetour land tour stop, e.g. Denali. country_code text latitude double precision longitude double precision description text url text points_of_interest jsonb — A list of points of interest, e.g. {"title": "Glacier Gardens", "description": "This 50-acre garden features species native to this temperate rainforest …"} images jsonb — The place's gallery as a URL array. embedding vector(1024) — Vector of name, description, and points of interest. products — Itinerary templates; one product has many voyages (departures). Same product = same route on different dates. id text — Product code, e.g. 'ASG070'. kind text — 'cruise' or 'cruisetour' (cruise + land tour package). name text region_code text region text — Destination region, e.g. 'Alaska', 'Caribbean'. subtrade_codes text[] images jsonb — Image URLs, keyed by role: 'hero' = destination/ship photo shown on a result card (NOT a map), 'map' = route-map graphic of the sailing (for a cruisetour, its cruise leg), 'detail_hero' = wide destination banner for the detail view, keyed by sub-trade rather than product. voyages…search instead.embedding column). Accepts a single string literal, e.g. embedding <=> embed('romantic'). Only the first 256 tokens are embedded. These tables carry an embedding column: excursion_reviews, excursions, lodges, places, ships, stateroom_categories, stateroom_subgroups. No other table has one. In particular products and voyages have none, so a whole trip has no vector of its own — match the mood on the ship, the ports it visits, or its excursions, and join back to the sailing. Express soft/semantic constraints in SQL with pgvector's cosine-distance operator <=>, always written as <table>.embedding, for example: ORDER BY ships.embedding <=> embed('romantic sunset dinner') LIMIT 20 WHERE (places.embedding <=> embed('glacier hike')) < 0.6 Treat the distance as a score — a bare embedding column can't be returned. PRODUCT KINDS: the catalog has two products.kind values — 'cruise' and 'cruisetour' (a cruise bundled with a land tour). A cruisetour is a cruise. When the user says "cruise" without singling out one kind, search both; add a kind filter only when they explicitly ask for one (e.g. "cruisetour packages", or "a cruise, not a land tour"). AVAILABILITY: only pricing.available says whether a sailing can still be booked — you MUST check it whenever you're picking sailings to recommend — including when the shopper mentioned no price or cabin. RESULTS: capped at ~500 KB of data, not a fixed row count — small rows pack more in. When more rows match than fit, truncated is true and the true match count is reported. Database date range: 2026-09-30 to 2028-11-18 TABLES (column comments carry units, joins, and valid values): ships — Princess ships. Join voyages.ship_code = ships.code. code text — 2-letter ship code, e.g. 'RP'. name text — Ship name, e.g. 'Royal Princess'. description text — Marketing prose about the ship. image_url text ship_version int spec jsonb — Label/value rows (guest capacity, crew, tonnage, …). stateroom_types text[] amenity_categories jsonb — Marketing groups (dining, entertainment) with items. zones jsonb — Deck zones (Forward/Midship/Aft). version_dates jsonb embedding vector(1024) — Vector of name, description, and dining/entertainment/amenity items. places — Everywhere a cruise stops. Whether a given stop is a port call or a land stop is a property of the stop, so read itinerary_days.stop_type for that, not this table. code text — 3-char place code, e.g. 'JNU'. name text — Full name, carrying the state or country, e.g. 'Juneau, Alaska'. is_port boolean — TRUE when the place is a port. A place can be both port and city at the same time — do NOT treat these as mutually exclusive. is_city boolean — TRUE when the place is a cruisetour land tour stop, e.g. Denali. country_code text latitude double precision longitude double precision description text url text points_of_interest jsonb — A list of points of interest, e.g. {"title": "Glacier Gardens", "description": "This 50-acre garden features species native to this temperate rainforest …"} images jsonb — The place's gallery as a URL array. embedding vector(1024) — Vector of name, description, and points of interest. products — Itinerary templates; one product has many voyages (departures). Same product = same route on different dates. id text — Product code, e.g. 'ASG070'. kind text — 'cruise' or 'cruisetour' (cruise + land tour package). name text region_code text region text — Destination region, e.g. 'Alaska', 'Caribbean'. subtrade_codes text[] images jsonb — Image URLs, keyed by role: 'hero' = destination/ship photo shown on a result card (NOT a map), 'map' = route-map graphic of the sailing (for a cruisetour, its cruise leg), 'detail_hero' = wide destination banner for the detail view, keyed by sub-trade rather than product. voyages…Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/princess-cruises"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/princess-cruises)