Skip to main content
Glama

pve_backup_job_create

Schedule persistent vzdump backups for PVE cluster guests. Dry-run by default; confirm=True to execute and create the job synchronously.

Instructions

MUTATION: create a PVE cluster backup job — a persistent vzdump schedule, distinct from a one-off pve_backup run. Dry-run by default; confirm=True to execute and returns synchronously (no task UPID). Config-only; existing backups are NOT affected. Guest selection is mutually exclusive — pass at most one of vmid, all_guests, or pool; exclude filters all_guests. To modify an existing job use pve_backup_job_update; to remove one use pve_backup_job_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoBackup mode: snapshot | suspend | stop; defaults to Proxmox's own default if omitted.
poolNoResource pool of guests to back up; mutually exclusive with vmid and all_guests.
vmidNoCSV of guest IDs to include; mutually exclusive with all_guests and pool.
job_idYesUnique ID for the new PVE backup job.
commentNoFree-text note stored on the job.
confirmNoGate: false returns a dry-run PLAN, true executes the creation.
enabledNoWhether the job is active; defaults to enabled if omitted.
excludeNoCSV of guest IDs to exclude when all_guests=True.
storageYesStorage ID the job writes backups to.
compressNoCompression algorithm for archives, e.g. zstd, gzip, lzo, or 0 (no compression).
scheduleYesProxmox calendar-event schedule string, e.g. 'sat 02:00' or a systemd.time-style spec.
all_guestsNoIf true, back up every guest on the cluster; mutually exclusive with vmid and pool.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses dry-run default behavior, the required confirm=True to execute, synchronous return without UPID, config-only nature, and the mutual exclusivity rule. No annotations provided, so description fully covers behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph with clear progression: purpose, distinction, behavior, constraints, alternatives. No unnecessary words, each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (13 parameters, many siblings) and presence of output schema, the description covers all critical aspects: purpose, default behavior, execution, return type, constraints, and related tools. It provides enough context for accurate tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, but the description adds behavioral context (dry-run, confirm), mutual exclusivity rules, and distinctions from other tools. This adds meaning beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a persistent PVE cluster backup job, distinguishes it from one-off backup runs, and mentions related tools for modification and deletion. The verb 'create' and resource 'PVE cluster backup job' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool vs one-off backup, and directs to pve_backup_job_update for modification and pve_backup_job_delete for removal. Also explains mutual exclusivity of guest selection parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server