edit_backup_job
Modify settings of a Claude-created Proxmox backup job, including schedule, retention, guests, storage, and enabled status, without touching the user's own jobs.
Instructions
Change a backup job Claude made (ID claude-…): any of its settings, or enabled to turn it off and on. keep {} goes back to the storage's own rule; a keep with numbers needs the Destroy switch (see create_backup_job). The user's own jobs cannot be changed here.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"host": "<host>",
"id": "<id>",
"reason": "<reason>"
},
"name": "edit_backup_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| all | No | Every guest of the host (but those in exclude). | |
| host | Yes | The host's id, from list_hosts. | |
| keep | No | How many backups to keep (Destroy switch). | |
| mode | No | ||
| notes | No | Each backup's note: {{guestname}} and {{vmid}} are filled in. | |
| vmids | No | The guests it backs up. | |
| reason | Yes | Why you are doing this, in a sentence. The user sees it in the approval window and in the log. | |
| comment | No | ||
| enabled | No | ||
| exclude | No | ||
| storage | No | ||
| compress | No | ||
| schedule | No | When: 03:00 · mon..fri 21:30 · sat,sun 02:00 · sun 04:00 · a Proxmox calendar event. |