Vacation Rental Management
You manage vacation rentals — Airbnb, VRBO, or your own direct bookings. Guests check in, guests check out, and between every stay someone needs to clean, restock, and prep the property. Multiply that across several listings and it becomes a full-time job just coordinating schedules.
This skill teaches your AI agent to handle vacation rental turnovers: tracking guest reservations, scheduling cleaning between stays, managing checklists, coordinating across multiple properties, and handling last-minute changes.
The Easy Way: TIDY
The fastest path is TIDY — an AI property management platform. Install the CLI and just tell it what you need in plain English:
CODEBLOCK0
Or connect via MCP (Claude Desktop, Claude Code, Cursor):
CODEBLOCK1
CODEBLOCK2
Once connected, your agent has access to message_tidy — send any request in natural language and TIDY handles the rest. See MCP Server Reference for full tool definitions.
The Manual Way
Without a platform like TIDY, managing vacation rental turnovers programmatically requires:
- 1. Reservation tracking — Build or integrate with a system to track check-in/check-out dates across properties
- Cleaner coordination — Find available cleaners, check their schedules, negotiate pricing, send booking requests
- Time-window management — Calculate the window between checkout and next check-in, account for cleaner travel time
- Checklist management — Create and assign property-specific checklists (linens, toiletries, lockbox reset)
- Status monitoring — Track whether the cleaner accepted, started, completed, or cancelled
- Multi-property juggling — Coordinate all of the above across multiple listings simultaneously
- Change handling — Guest extends their stay? New booking comes in? Rebuild the schedule
If you want to build this yourself, TIDY's REST API exposes every step individually. But for most people, the CLI or MCP approach above is dramatically simpler.
Core Workflow: Guest Turnover
The fundamental workflow for vacation rentals: a guest checks out, you need a turnover clean, and a new guest checks in.
Step 1: Record the Reservation
Tell TIDY about the guest stay:
CODEBLOCK3
Or via MCP:
CODEBLOCK4
Or via REST API:
CODEBLOCK5
Step 2: Schedule the Turnover Clean
CODEBLOCK6
TIDY will find available cleaners, check pricing, and book the job in the checkout-to-checkin window.
For direct REST API booking, you'd specify the time window:
CODEBLOCK7
Step 3: Attach a Checklist
CODEBLOCK8
To-do lists can include items like: change linens, restock toiletries, check appliances, reset lockbox code.
Step 4: Monitor Status
CODEBLOCK9
Booking statuses: scheduled → in_progress → completed. Also cancelled or failed.
Managing Reservations
View All Reservations
CODEBLOCK10
REST: GET /api/v2/guest-reservations (filter by ?address_id=123)
Create a Reservation
CODEBLOCK11
Cancel a Reservation
CODEBLOCK12
REST: INLINECODE8
Handle Changes
Guest extended their stay? Just tell TIDY:
CODEBLOCK13
Multi-Property Coordination
Set Up Properties
Each property needs an address with access instructions for cleaners:
CODEBLOCK14
REST API address creation includes structured parking and access notes — see REST API Reference.
View All Properties
CODEBLOCK15
Property-Specific Checklists
Different properties may need different turnover checklists:
CODEBLOCK16
REST: INLINECODE9
Common Scenarios
Here are natural-language requests your agent can send directly to TIDY:
Same-day turnover:
"Guest checks out at 11am Saturday, new guest arrives at 3pm. Schedule a turnover clean at 123 Main St."
Weekly schedule check:
"What cleanings are scheduled across all my properties this week?"
New listing setup:
"Set up a new Airbnb listing at 789 Pine St, Denver CO 80202. Gate code 4321, park in visitor lot. Schedule a deep clean before the first guest arrives on March 28."
Guest extension:
"Cancel the turnover clean for 456 Oak Ave — the guest extended through Wednesday."
Availability check:
"Is there availability for a turnover clean at 123 Main St on Saturday between 11am and 2pm?"
Bulk reservation import:
"I have three reservations this month at the lake house: March 5-8, March 12-15, and March 20-25. Schedule turnover cleans after each checkout."
MCP Server
For agents that support MCP (Claude Desktop, Claude Code, Cursor), connect directly to TIDY's MCP server. This gives your agent 5 tools:
- -
login / signup — authenticate - INLINECODE12 — send any request in natural language (async)
- INLINECODE13 — poll for the result
- INLINECODE14 — view past requests
The message_tidy tool is asynchronous — after calling it, poll get_message_tidy with the returned ID until is_complete is true.
Full tool definitions and setup: MCP Server Reference
REST API
For custom integrations or direct API access, TIDY exposes REST endpoints for every operation:
- - Guest reservations: create, list, get, delete
- Bookings: create, list, get, update, cancel, reschedule
- Addresses: full CRUD with parking/access notes
- To-do lists: list by property
- Booking availabilities: check time slots
- Job acceptance probabilities: preview likelihood of pro accepting
Full endpoint documentation: REST API Reference
Authentication details: Authentication
Error Handling & Tips
Polling: message_tidy is asynchronous. Always poll get_message_tidy every 3-5 seconds until is_complete is true. Never return a pending response to the user.
Overlapping reservations: If you create a reservation that overlaps with an existing one at the same address, TIDY will flag it. Resolve the conflict before scheduling cleanings.
Tight turnovers: If the window between checkout and next check-in is very short (under 2 hours), consider a shorter service type or adjusting times. Check booking-availabilities to see what's possible.
Same-day changes: Cancellation and rescheduling are available, but last-minute changes (same day) may have limited cleaner availability.
Context IDs: When following up on a specific booking or reservation, pass the relevant ID in the context parameter to help TIDY scope the request:
CODEBLOCK17
Also see: cleaning-maintenance — if you need ongoing cleaning or maintenance management that isn't tied to guest turnovers.
度假租赁管理
您管理度假租赁物业——Airbnb、VRBO或您自己的直订房源。客人入住、客人退房,每次住宿之间都需要有人清洁、补货和准备物业。如果同时管理多个房源,光是协调日程就成了一项全职工作。
这项技能教会您的AI代理处理度假租赁的周转工作:跟踪客人预订、安排住宿间隙的清洁、管理检查清单、协调多个物业,以及处理最后一刻的变更。
简便方法:TIDY
最快的途径是TIDY——一个AI物业管理平台。安装CLI后,直接用日常英语告诉它您需要什么:
bash
安装
brew install tidyapp/tap/tidy-request # 或:npm i -g @tidydotcom/cli
创建账户
tidy-request signup
就这样。现在只需告诉它您需要什么:
tidy-request 在周六上午11点退房后,安排123 Main St的周转清洁
tidy-request 我的海滩别墅有客人周五下午3点入住,周日上午11点退房
tidy-request 本周我所有物业安排了哪些清洁?
tidy-request 取消456 Oak Ave的周转清洁,客人延长了住宿
或通过MCP连接(Claude Desktop、Claude Code、Cursor):
bash
Claude Code
claude mcp add tidy --transport http https://public-api.tidy.com/mcp
json
// Claude Desktop — 添加到 claudedesktopconfig.json
{
mcpServers: {
tidy: {
url: https://public-api.tidy.com/mcp
}
}
}
连接后,您的代理可以访问messagetidy——用自然语言发送任何请求,TIDY会处理其余事项。完整工具定义请参见MCP服务器参考。
手动方法
如果没有TIDY这样的平台,以编程方式管理度假租赁周转需要:
- 1. 预订跟踪——构建或集成一个系统来跟踪各物业的入住/退房日期
- 清洁工协调——寻找可用的清洁工、检查他们的日程、协商价格、发送预订请求
- 时间窗口管理——计算退房和下次入住之间的时间窗口,考虑清洁工的出行时间
- 检查清单管理——创建和分配物业特定的检查清单(床单、洗漱用品、密码箱重置)
- 状态监控——跟踪清洁工是否接受、开始、完成或取消
- 多物业协调——同时协调上述所有事项跨多个房源
- 变更处理——客人延长住宿?有新预订?重新构建日程
如果您想自己构建,TIDY的REST API提供了每个步骤的单独接口。但对大多数人来说,上述CLI或MCP方法要简单得多。
核心工作流程:客人周转
度假租赁的基本工作流程:客人退房,您需要周转清洁,然后新客人入住。
第1步:记录预订
告诉TIDY客人的住宿信息:
bash
tidy-request 我在123 Main St有客人3月20日下午3点入住,3月25日上午11点退房
或通过MCP:
message_tidy(客人3月20日下午3点入住,3月25日上午11点退房,地址123 Main St)
或通过REST API:
bash
curl -X POST https://public-api.tidy.com/api/v2/guest-reservations \
-H Authorization: Bearer YOUR_TOKEN \
-H Content-Type: application/json \
-d {
address_id: 123,
check_in: { date: 2026-03-20, time: 15:00 },
check_out: { date: 2026-03-25, time: 11:00 }
}
第2步:安排周转清洁
bash
tidy-request 安排123 Main St在3月25日上午11点退房后的周转清洁,需要在下午3点前完成以迎接下一位客人
TIDY会找到可用的清洁工、检查价格,并在退房到入住的窗口期内预订工作。
对于直接的REST API预订,您需要指定时间窗口:
bash
curl -X POST https://public-api.tidy.com/api/v2/jobs \
-H Authorization: Bearer YOUR_TOKEN \
-H Content-Type: application/json \
-d {
address_id: 123,
servicetypekey: turnovercleaning.twoandahalf_hours,
startnoearlier_than: { date: 2026-03-25, time: 11:00 },
endnolater_than: { date: 2026-03-25, time: 15:00 }
}
第3步:附加检查清单
bash
tidy-request 将周转检查清单添加到3月25日123 Main St的清洁工作中
待办事项清单可以包括:更换床单、补充洗漱用品、检查电器、重置密码箱密码。
第4步:监控状态
bash
tidy-request 123 Main St的周转清洁状态如何?
预订状态:已安排 → 进行中 → 已完成。还有已取消或失败。
管理预订
查看所有预订
bash
tidy-request 显示所有即将到来的客人预订
REST:GET /api/v2/guest-reservations(按?address_id=123过滤)
创建预订
bash
tidy-request 湖景房有新客人:4月5日下午4点到达,4月10日上午10点离开
取消预订
bash
tidy-request 取消789 Pine St 4月5日的预订
REST:DELETE /api/v2/guest-reservations/:id
处理变更
客人延长了住宿?直接告诉TIDY:
bash
tidy-request 123 Main St的客人将住到3月27日而不是3月25日。重新安排周转清洁。
多物业协调
设置物业
每个物业需要一个地址,并附上清洁工的进入说明:
bash
tidy-request 添加我在456 Oak Ave, Austin TX 78701的物业。大门密码是1234,停在车道上。
tidy-request 添加我在789 Coastal Dr, Galveston TX 77550的海滩别墅。钥匙在密码箱里,密码5678。只能街边停车。
REST API地址创建包括结构化的停车和进入说明——请参见REST API参考。
查看所有物业
bash
tidy-request 显示我所有物业及其即将到来的清洁安排
物业特定检查清单
不同的物业可能需要不同的周转检查清单:
bash
tidy-request 海滩别墅有哪些待办清单?
REST:GET /api/v2/to-do-lists?address_id=789
常见场景
以下是您的代理可以直接发送给TIDY的自然语言请求:
同日周转:
客人周六上午11点退房,新客人下午3点到达。安排123 Main St的周转清洁。
每周日程检查:
本周我所有物业安排了哪些清洁?
新房源设置:
在789 Pine St, Denver CO 80202设置一个新的Airbnb房源。大门密码4321,停在访客停车场。在3月28日第一位客人到达前安排一次深度清洁。
客人延期:
取消456 Oak Ave的周转清洁——客人延长住宿到周三。
可用性检查:
周六上午11点到下午2点之间,123 Main St是否有周转清洁的可用时段?
批量预订导入:
本月湖景房有三个预订:3月5-8日、3月12-15日和3月20-25日。每次退房后安排周转清洁。
MCP服务器
对于支持MCP的代理(Claude Desktop、Claude Code、Cursor),直接连接到TIDY的MCP服务器。这为您的代理提供5个工具:
- - login / signup — 身份验证
- messagetidy — 用自然语言发送任何请求(异步)
- getmessagetidy — 轮询获取结果
- listmessages_tidy — 查看历史请求
messagetidy工具是异步的——调用后,使用返回的ID轮询getmessagetidy,直到iscomplete为true。
完整工具定义和设置:MCP服务器参考
REST API
对于自定义集成或直接API访问,TIDY为每个操作提供REST端点:
- - 客人预订:创建、列出、获取、删除
- 预订:创建、列出、获取、更新、取消、重新安排
-