Skip to main content
Glama

List backup jobs

proxmox_list_backup_jobs
Read-only

List cluster scheduled backup (vzdump) jobs with schedule, next run, target storage, mode, covered guests, compression and retention. Check which guests each job protects.

Instructions

List the cluster's scheduled backup (vzdump) jobs: schedule, next run, enabled, target storage, mode, which guests (all/VMID list/pool, exclusions), compression and retention. See proxmox_get_backup_job for one job with the guests and disks it covers, and proxmox_list_unbacked_guests for guests no job covers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_backup_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety is covered. Beyond those, the description discloses the content of each returned job record (guest selection modes, exclusions, retention), which is meaningful behavioral context. It does not mention output volume on large clusters or how the guest-mode field varies (all/VMID list/pool), leaving some gaps.

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?

Two sentences, both front-loaded and dense: sentence one states scope and returned attributes, sentence two does the sibling routing. Every clause carries information and nothing is redundant.

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

Completeness4/5

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

With no output schema, listing the returned job attributes is exactly the right compensation, and the sibling routing completes the picture for a read-only list tool. Minor gaps: no guidance on the undocumented 'fields' parameter or on result size/pagination for large clusters.

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

Parameters3/5

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

Schema coverage is 67%: 'raw' and 'search' are documented in the schema, but the 'fields' array has no description anywhere. The description says nothing about any of the three parameters, so it neither compensates for the uncovered 'fields' parameter nor adds semantics beyond the schema. Baseline 3 reflects adequate but non-contributing parameter treatment.

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 opens with a specific verb and resource plus scope ('the cluster's scheduled backup (vzdump) jobs') and then enumerates the exact attributes returned: schedule, next run, enabled, target storage, mode, guest selection, compression and retention. This makes it immediately separable from proxmox_get_backup_job and proxmox_list_unbacked_guests, which are named explicitly.

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?

It names two alternatives with the condition that selects each: proxmox_get_backup_job for 'one job with the guests and disks it covers' and proxmox_list_unbacked_guests for 'guests no job covers'. An agent can route without opening any schema.

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

Deploy Server

Other Tools