hostaway-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOSTAWAY_KIT_NOW | No | ISO timestamp that pins 'now' for SLA math (used by tests). | |
| HOSTAWAY_ACCOUNT_ID | No | Hostaway account id (client_id on POST /v1/accessTokens). Required only for live reads; if unset, the server serves bundled fixtures. | |
| HOSTAWAY_CLIENT_SECRET | No | Client secret from the Hostaway dashboard. Required only for live reads; if unset, the server serves bundled fixtures. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_listingsA | List Hostaway listings. Defaults to GET /v1/listings?specialStatus[]=active. Optional availabilityDateStart/End + availabilityGuestNumber filter the list the same way Hostaway does. Amenities are amenityId values, not free-text names. Check-in/out hours are 0–23. Denylisted access and invoicing fields are stripped. |
| get_listingA | Retrieve one listing via GET /v1/listings/{id}?includeResources=1. House rules, check-in hours (0–23), amenityId values, and photos are included. wifiPassword, door codes, and invoicing contacts are stripped. |
| get_calendarA | Retrieve listing calendar via GET /v1/listings/{id}/calendar?includeResources=1. Each day has status (available/blocked/reserved/pending), isAvailable, and price (null means unknown — do not invent a rate). Nested reservations are denylist-stripped. |
| list_reservationsA | List reservations via GET /v1/reservations. Read-only. doorCode / doorCodeVendor / doorCodeInstruction are stripped. Create reservation is not implemented. |
| list_conversationsB | List inbox threads via GET /v1/conversations?includeResources=1. Nested Reservation objects are denylist-stripped. |
| list_messagesA | List messages in a thread via GET /v1/conversations/{id}/messages. Read-only. There is no send tool. |
| inbox_triageB | Unanswered / SLA view Hostaway's inbox does not compute. A thread is unanswered when the latest message is incoming (or hasUnreadMessages with no later host reply). Default SLA is 2 hours. Does not send replies. |
| draft_replyA | Suggested reply grounded in THAT listing's fields, house rules, amenityId values, and calendar prices. Never invent rates (use calendar or say unknown). Never include wifi or door codes. Never POSTs a message — send is always false and there is no send endpoint. |
| report_occupancyA | Occupancy and blocked holes computed from calendar reads. Occupancy = reserved nights / (reserved + available). Blocked holes are consecutive blocked/hardBlock days. Not an owner statement. No financials. |
| report_inboxB | Unanswered thread counts by listing, computed from conversation reads. Not a Hostaway owner statement. |
| report_completenessB | Listing completeness from reads: missing photos, missing house rules, missing amenities (empty listingAmenities). Not a financial report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct resource or report: reservations, conversations, messages, listings, calendar, and aggregate reports. Even the inbox-related tools operate at clearly different granularities: list_conversations lists threads, inbox_triage identifies unanswered threads, and report_inbox aggregates unanswered-thread counts by listing.
All tool names are lowercase snake_case verb_noun: list_* for collections, get_* for single resources, report_* for computed summaries, plus inbox_triage and draft_reply. The naming pattern is consistent and predictable.
11 tools is well within the ideal 3-15 range, and each tool covers a meaningful, non-redundant aspect of Hostaway read-only operations and reporting. There are no filler tools or excessive overlapping endpoints.
The read/triage/draft workflow is well covered, but the server is explicitly read-only: create/update/delete operations for reservations and listings are absent, and there is no send-message tool. These are notable gaps, though the descriptions openly acknowledge them and no financial/owner-statement tools are claimed.