Skip to content
DEConsole
DEVELOPERS / DEVELOPERS
View as MarkdownDownload Markdown
Open in ChatGPTOpen in Claude

Page unavailable? Copy its Markdown and paste it into your chat.

delete_event

Behavior, inputs, outputs and permissions for delete_event.

Reviewed · 2026-09-20 / Ridian

This reference is generated from the published tool contract.

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.

Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.

calendar:read, calendar:write

Consent and boundaries

{
"$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
}
{
"$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
}

Check the tool result for errors. Do not blindly retry writes after a timeout. Check the calendar state first.

Error handling

RIDIAN

Ask the docs

Enter to send · ⇧ Enter for new line

No passwords or calendar contents. Check AI answers against their sources. AI & privacy