delete_inbox_thread

This reference is generated from the published tool contract.

Behavior and boundaries

Permanently deletes an entire thread only from trash and only when expectedSequence equals the latest observed sequence. Read get_inbox_thread first. A concurrent new message rejects deletion; reread and decide again. Access is denied immediately, stored messages/attachments are purged in batches and storage is released as each batch completes. Separately saved drafts and forwarded copies remain; reply drafts whose source was deleted cannot send until their reply reference is removed. Queued sends cannot dispatch after deletion, but mail already handed to the provider cannot be recalled. Missing threads after an uncertain response are already unavailable; never create replacement mail as a retry. No automatic trash expiry.

Permissions

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

inbox:write

Consent and boundaries

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "expectedSequence": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "id",
    "expectedSequence"
  ],
  "additionalProperties": false
}

Output

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

Errors and retries

Check the tool result for errors. Do not blindly retry writes after a timeout. Check the current resource or send status first.

Error handling