Tools by area
Delete operations are intentionally not exposed over MCP. Use the REST API if you need them.
Booking a meeting
An agent books a meeting in three steps: find the scheduling page and event type (list_scheduling_pages → list_event_types), fetch open slots for a date with get_available_slots (working hours intersected with the host’s live calendar free/busy), then call book_meeting with one of the returned slots. Booking creates the meeting, sends calendar invites to both sides, and triggers configured workflows; a taken slot returns a 409 so the agent can pick another. The team_id on these calls is always derived from your API key server-side — it cannot be overridden.
Rate limits & behavior
MCP tool calls execute the corresponding/api/v1 endpoints internally, so REST API rate limits apply unchanged. List tools return the same paginated envelope as the REST API (data plus meta.total / meta.page / meta.total_pages); pass page and per_page arguments to page through results.