# delete_created_calendar

Behavior, inputs, outputs and permissions for delete_created_calendar.

Source: https://docs.getridian.com/developers/tools/delete_created_calendar/
Language: en
Reviewed: 2026-09-20

This reference is generated from the published tool contract.

## Behavior and boundaries

Permanently deletes an entire secondary Google calendar only after the user explicitly approves permanent deletion of its exact visible name. Ridian additionally requires server-side provenance proving that the same user created that exact calendar with create_calendar. Pass the original create_calendar requestId, the exact calendarName, and confirmPermanentDeletion=true; no calendar ID is accepted from the client. It cannot delete primary, pre-existing, imported, or manually created calendars. All events in that calendar are permanently deleted by Google. Repeating the same deletion unchanged is safe. cleanupPending=true means Google already deleted the calendar but Ridian still has bounded local cleanup work; call this tool again unchanged.

## Permissions

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

`calendar:read`, `calendar:manage`

[Consent and boundaries](https://docs.getridian.com/developers/authentication/)

## Input

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "createRequestId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "description": "Exact requestId originally passed to create_calendar for the calendar that should be permanently deleted."
    },
    "calendarName": {
      "type": "string",
      "minLength": 1,
      "maxLength": 512,
      "description": "Exact visible name of the Ridian-created calendar the user explicitly approved for permanent deletion."
    },
    "confirmPermanentDeletion": {
      "type": "boolean",
      "const": true,
      "description": "Must be true and may only be supplied after the user explicitly approves permanent deletion of calendarName and all events inside it."
    }
  },
  "required": [
    "createRequestId",
    "calendarName",
    "confirmPermanentDeletion"
  ],
  "additionalProperties": false
}
```

## Output

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "const": true
    },
    "deleted": {
      "type": "boolean"
    },
    "cleanupPending": {
      "type": "boolean"
    }
  },
  "required": [
    "ok",
    "deleted",
    "cleanupPending"
  ],
  "additionalProperties": false
}
```

## Errors and retries

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

[Error handling](https://docs.getridian.com/developers/errors/)