Skip to main content
Glama

pbs_group_delete

Delete an entire backup group and all its snapshots from a Proxmox Backup Server datastore. Use with caution—this operation is irreversible and removes all recovery points.

Instructions

MUTATION: delete an ENTIRE backup group including ALL its snapshots.

RISK_HIGH — bulk-destructive: one call removes every recovery point for this guest/host in this namespace; strictly more destructive than pbs_snapshot_delete (one snapshot) and the same class as pbs_namespace_delete(delete_groups=True). No undo. Check pbs_groups_list / pbs_snapshots_list first — the PLAN deliberately does not pull that content in itself. Dry-run by default; confirm=True executes (DELETE /admin/datastore/{store}/groups) and returns {"status": "ok", "result": {removed-groups, removed-snapshots, protected-snapshots}} — a SYNCHRONOUS stats object, not a task UPID; verify the counters, especially protected-snapshots when error_on_protected=False (a nonzero value means a PARTIAL delete). Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoNamespace; omit for the root namespace.
storeYesPBS datastore name.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the deletion.
backup_idYesBackup group ID whose ENTIRE group (all snapshots) will be deleted.
backup_typeYesBackup type: vm, ct, or host.
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.
error_on_protectedNoUpstream default TRUE: fail if the group contains any protected snapshot. False = delete all UNPROTECTED snapshots, keep protected ones, and SUCCEED as a partial delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully explains the mutation, bulk-destructive nature, no undo, dry-run default, synchronous return stats, and the role of error_on_protected. All behavioral traits are disclosed.

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

Conciseness4/5

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

Well-structured with clear sections and front-loaded purpose. While slightly dense with details, every sentence adds value and there is no redundancy.

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 (7 parameters, output schema exists), the description covers prerequisites, dry-run behavior, return object interpretation, partial deletion scenarios, and configuration needs. It leaves no important gaps.

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 coverage is 100%, so baseline is 3. Description adds significant value by explaining the confirm parameter's effect on dry-run vs execution, the return object details, and the error_on_protected behavior. This goes 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?

Explicitly states the action 'delete an ENTIRE backup group including ALL its snapshots' and distinguishes from similar tools like pbs_snapshot_delete (one snapshot) and pbs_namespace_delete. The verb and resource are clear.

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?

Provides explicit when-to-use guidance: recommends checking pbs_groups_list/pbs_snapshots_list first, explains dry-run default, and clarifies the effect of confirm=True. Also clarifies alternatives and partial delete behavior.

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