preview_delete_sync

This reference is generated from the published tool contract.

Behavior and boundaries

Shows what deleting one of the user’s own sync pairs would remove, without changing anything: how many directions (legs) the pair has and how many copies Ridian manages in the target calendar(s). Deleting removes those copies; the original events stay. Returns a confirmToken for delete_sync, valid only while the pair stays the same. Use a ref from a current list_syncs result.

Permissions

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

sync:read

Consent and boundaries

Input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ref": {
      "type": "string",
      "minLength": 1,
      "maxLength": 40
    }
  },
  "required": [
    "ref"
  ],
  "additionalProperties": false
}

Output

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "const": true
    },
    "ref": {
      "type": "string"
    },
    "legs": {
      "type": "number"
    },
    "managedCopies": {
      "type": "number"
    },
    "confirmToken": {
      "type": "string"
    }
  },
  "required": [
    "ok",
    "ref",
    "legs",
    "managedCopies",
    "confirmToken"
  ],
  "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