Create calendar event
create_calendar_eventCreate and schedule calendar events or meetings for the authenticated user, invite attendees with iMIP notifications, and set recurrence, reminders, or all-day personal time blocks.
Instructions
Create, schedule or book a new calendar event or meeting on the user’s calendar, and invite people to it with the authenticated user as organizer. Attendees receive iMIP invitations (pass notify: "none" to suppress them); omit attendees for a personal event — a block of the user’s own time. For an all-day event (a day off, a vacation) pass start/end as dates. Pass recurrence for a repeating series (e.g. a weekly team meeting) in one call, and reminderMinutesBefore to be reminded. Defaults to the user’s default calendar.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"end": "<end>",
"start": "<start>",
"title": "<title>"
},
"name": "create_calendar_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | Event end as ISO 8601 (see `timeZone`). For an all-day event a date, exclusive: the day after the last day (a day off on 2026-10-03 ends 2026-10-04). | |
| start | Yes | Event start as ISO 8601 (see `timeZone`), or a date (2026-10-03) for an all-day event. | |
| title | Yes | ||
| notify | No | Whether to send the iMIP invitations. `all` (default) sends them; `none` invites nobody. | |
| showAs | No | Whether this event counts as busy time. `busy` (default) means it does; `free` means it does not — for holds, reminders and travel buffers the user does not want counted against their availability. Inviting people makes an event count as busy time, so `free` is refused when `attendees` are given. | |
| location | No | ||
| timeZone | No | IANA zone for start/end, e.g. Europe/Berlin: their clock digits are read as wall-clock time here, overriding any offset. Defaults to the account timezone, then UTC. | |
| attendees | No | Email addresses to invite; each receives an iMIP invitation. Omit for a personal event — a block of the user’s own time — with no invitations sent. | |
| recurrence | No | Repeat rule; omit for a one-off event. start/end are its first occurrence. Either a raw RFC 5545 RRULE ("FREQ=WEEKLY;BYDAY=TH", "FREQ=DAILY;COUNT=10") or {frequency, interval?, byDay?, until?|count?}. Use at most one of until/count; The object’s `until` is ISO (2026-12-31 or 2026-12-31T00:00:00Z); a raw UNTIL is compact (20261231 or 20261231T000000Z). Either is converted to match the event (a date on an all-day series). A raw rule is only lightly validated, so a malformed one fails later at the server. | |
| calendarUrl | No | ||
| description | No | ||
| reminderMinutesBefore | No | Remind the user this many minutes before the start (e.g. 30); omit for no reminder. An all-day event starts at 00:00, so 900 = 09:00 the day before. |