Skip to main content
Glama

List backups

proxmox_list_backups
Read-only

List Proxmox VE backup archives across all backup storages, newest first, filtering by VM/container, storage, node, or age to find the volume ID for restore or management.

Instructions

List backup archives across every storage that holds backups (local dirs, NFS/CIFS, Proxmox Backup Server...), newest first: volume ID, guest, time, size, format, notes, protection and PBS verification state. Filter by vmid, type, storage, node or age. Shared storages are listed once. Use the volid with proxmox_restore_backup, proxmox_get_backup_config, proxmox_update_backup or proxmox_delete_backup.

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_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoOnly storages on this node
typeNoOnly VM or only container backups
vmidNoOnly backups of this guest
limitNoMaximum number of results (default 100)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
storageNoOnly this storage
newer_than_daysNoOnly backups newer than this many days
older_than_daysNoOnly backups older than this many days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds ordering ('newest first'), the exact result shape, and the non-obvious dedupe rule ('Shared storages are listed once'). It does not mention pagination/default-limit behavior, though the schema covers the limit parameter.

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?

Three tight sentences, front-loaded with scope, then returned fields, then the hand-off to consuming tools. No redundant or filler wording.

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, the description compensates by enumerating returned fields (volume ID, guest, time, size, format, notes, protection, PBS verification state). Combined with annotations, this is sufficient for a read-only 10-parameter lister; only pagination/default-limit behavior is left implicit in the schema.

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 description coverage is 90%, so the baseline is 3. The description's 'Filter by vmid, type, storage, node or age' merely restates parameters already documented in the schema and says nothing about raw, fields, search, or limit semantics.

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?

States a specific verb and resource ('List backup archives'), the full breadth of scope ('across every storage that holds backups'), and enumerates the returned fields so the agent knows this is the cross-storage archive index rather than a per-guest or job listing. Deduplication of shared storages further pins down its behavior.

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

Usage Guidelines4/5

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

Explicitly routes the output onward: 'Use the volid with proxmox_restore_backup, proxmox_get_backup_config, proxmox_update_backup or proxmox_delete_backup', which tells the agent this is the discovery step preceding those tools. It also names the filterable axes. It lacks explicit when-not-to-use guidance versus proxmox_list_backup_files or proxmox_list_backup_jobs.

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