pterodactyl-mcp

Delete a Pterodactyl backup

ptero_delete_backup

DestructiveIdempotent

Permanently delete a server backup after showing a preview and obtaining explicit confirmation. Locked backups must be unlocked first.

Instructions

Permanently delete one backup. IRREVERSIBLE — there is no undo and no confirmation from the panel beyond this tool.

Requires PTERODACTYL_ALLOW_DELETE=true. Requires confirmation: the first call without confirmation_token returns a preview (name, size, created_at) and a token instead of deleting anything — THAT PREVIEW IS FOR THE HUMAN, show it and wait for approval before calling again with the token. A locked backup cannot be deleted here at all; unlock it in the panel first.

Input Schema

TableJSON Schema

Name	Required	Description
`server`	No	Server short identifier (e.g. 1a2b3c4d). Omit to use PTERODACTYL_DEFAULT_SERVER. Call ptero_list_servers to discover valid identifiers.
`dry_run`	No	When true, validate and preview the change without performing it. Nothing is modified and no confirmation token is issued. Use this to reason about an operation before committing to it.
`backup_uuid`	Yes	UUID of the backup to delete (from ptero_list_backups).
`confirmation_token`	No	Two-phase confirmation token. Leave this out on the first call: the tool will refuse to act and instead return a preview of exactly what would change, plus a single-use token that expires in 120 seconds. THE PREVIEW IS FOR THE HUMAN — show it to the user in your reply and let them decide. Do not silently round-trip the token back in an immediate second call. Only call again with the token once the user has seen the preview and approved it. The token is bound to a hash of these exact arguments, so changing any argument invalidates it.

Output Schema

TableJSON Schema

Name	Required	Description
`uuid`	No
`reason`	No	Why the call was refused.
`server`	Yes
`status`	Yes	success = the change was made. refused = a guardrail blocked it (see reason/variable). dry_run = nothing changed; preview shows what would. needs_confirmation = nothing changed; SHOW the preview to the human and, only if they agree, call again with confirmation_token.
`message`	No
`preview`	No	What would / did change.
`variable`	No	Environment variable that caused the refusal.
`backup_id`	No	UUID of the automatic pre-change backup, if one was taken.
`expires_in_s`	No
`confirmed_via`	No
`confirmation_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool as destructive and idempotent, but the description adds crucial context beyond them: irreversibility with no undo, the no-op preview on first call, the single-use expiring token, the requirement for PTERODACTYL_ALLOW_DELETE=true, and the locked-backup failure mode.

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?

The description is dense but compact, with the most important warning front-loaded. Each sentence contributes operational value, and the all-caps emphasis is used sparingly for genuinely critical points like IRREVERSIBLE and the human-preview requirement.

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?

Between the detailed schema, the output schema, and the annotations, the description covers the remaining behavioral gaps: environment requirements, safe two-phase deletion, human approval, and a clear exclusion for locked backups. An agent has everything needed to invoke this tool correctly.

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 100%, and the schema already explains server, dry_run, backup_uuid, and confirmation_token in detail. The description reinforces the confirmation-token flow but does not add significant per-parameter meaning beyond the schema, so baseline 3 is appropriate.

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: 'Permanently delete one backup.' This unambiguously distinguishes the tool from sibling backup operations like ptero_list_backups and ptero_create_backup, and from other delete tools like ptero_delete_file.

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 gives explicit when-to-use and when-not-to-use guidance: the environment variable prerequisite, the two-phase confirmation flow, the rule to show the preview to the human and wait for approval, and the locked-backup exclusion with the alternative action ('unlock it in the panel first').

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