delete_event
Behavior, inputs, outputs and permissions for delete_event.
Reviewed · 2026-09-20 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “Behavior and boundaries”Permanently deletes exactly one event identified by calendarId and eventId. Immediately before deletion, the provider must confirm that it is an organizer-owned standalone event without guests or conference data; other events are rejected. Use list_events first and proceed only when exactly one intended event matches and canEdit=true. Repeating the same deletion is safe.
Permissions
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
calendar:read, calendar:write
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "calendarId": { "type": "string", "minLength": 1 }, "eventId": { "type": "string", "minLength": 1, "maxLength": 2048 } }, "required": [ "calendarId", "eventId" ], "additionalProperties": false}Output
Section titled “Output”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "ok": { "type": "boolean", "const": true }, "eventId": { "type": "string" }, "changed": { "type": "boolean" } }, "required": [ "ok", "eventId", "changed" ], "additionalProperties": false}Errors and retries
Section titled “Errors and retries”Check the tool result for errors. Do not blindly retry writes after a timeout. Check the calendar state first.