Skip to content
Tools

The same plan as generate_hooks: an edit decision list of existing segments and a hook for each variant. cut_on_beat uses the beats stored for each file. Nothing is rendered.

Access token · edit · Changes account data

Parameters

batch_id string required
View schema
batch_id schema
{
  "type": "string",
  "format": "uuid",
  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"
}
cut_on_beat boolean optional

Move each planned cut onto a nearby beat from the native tracker.

View schema
cut_on_beat schema
{
  "description": "Move each planned cut onto a nearby beat from the native tracker.",
  "type": "boolean"
}

Request example

Tool request · example
{
  "name": "plan_variants",
  "arguments": {
    "batch_id": "00000000-0000-4000-8000-000000000001"
  }
}

Replace example values with ids and arguments read from your own Heavenly account. This example does not execute a tool.

Returns

The tool result from Heavenly’s workspace, encoded as MCP text content. The connector returns isError when an argument, permission, plan or account check fails.

Account access and permissions are checked by Heavenly. See errors for failure handling.