MCP server for the Hostaway vacation rental PMS API
Hostaway MCP demonstrates solid fundamentals: all 18 tools have clear verb-noun naming (list_, get_, create_, update_, delete_, send_), complete input schemas with type definitions, and descriptions ranging 50 - 180 chars. However, several gaps prevent a higher score. Parameter descriptions are minimal (often 1 - 2 words: 'Listing ID', 'Reservation ID') and lack actionable constraints (e.g., date format, enum values, limits). Output schemas are not documented, callers cannot predict response structure. Error handling is basic (generic 'API error' messages) with no recovery guidance. Tool composition is sound (single responsibility, proper chaining via IDs), but descriptions omit WHEN to use each tool vs. similar ones (e.g., list_reservations vs. list_reservations_by_property). Security is well-handled (secrets via env vars, read-only mode), but no tool annotations (readOnlyHint, destructiveHint) are present despite 5 write/destructive tools.
Block dates on a listing calendar. Blocked if HOSTAWAY_READ_ONLY is true.
Remove a calendar block from a listing. Blocked if HOSTAWAY_READ_ONLY is true.
Returns availability and pricing calendar for a listing within a date range.
Returns the full message thread for a conversation.
Analyses the calendar to find gap nights (short unbooked gaps between reservations). Useful for identifying revenue optimization opportunities.
Get full details for a single listing by ID.
Output schemas not documented. Callers cannot predict response structure (fields, types, nesting). Forces LLMs to guess downstream field names and risks failed chaining.
Parameter descriptions are minimal (1 - 2 words: 'Listing ID', 'Reservation ID'). Lack actionable constraints: date format (YYYY-MM-DD stated in some but not all), enum values for status/channel, numeric limits (limit max 100 mentioned in list_reservations but not others).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite 5 write/destructive tools (update_reservation_host_note, create_calendar_block, delete_calendar_block, send_message). LLMs cannot infer safety/retry semantics.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Returns all custom field values for a listing as a readable name-value map.
Get all photos/images for a listing. Returns image URLs, captions, and sort order.
Returns a payout-style report for reconciliation against Airbnb/Booking.com statements. Per-reservation rows with financials.
Get full details of a single reservation by ID.
Returns the financial breakdown for a single reservation (revenue, payout, fees, commission, taxes).
Returns aggregated revenue across all or selected listings for a date range. Includes per-listing breakdown and totals.
Returns recent guest conversations with optional filters.
Returns all active listings with key metadata (name, URLs, capacity, location).
List reservations with optional filters for listing, dates, status, and channel.
Returns all current and upcoming reservations grouped by listing name. Useful for a portfolio overview.
Send a message to a guest in a conversation. Blocked if HOSTAWAY_READ_ONLY is true.
Update the internal host note on a reservation. Blocked if HOSTAWAY_READ_ONLY is true.
Error handling is generic. formatApiError() returns 'Hostaway API error: ...' with no recovery guidance. LLMs cannot determine if error is retryable, user-fixable, or fatal.
Tool descriptions do not explain WHEN to use each tool vs. similar ones. E.g., list_reservations vs. list_reservations_by_property distinction unclear; get_listing vs. get_listing_custom_fields unclear.