pterodactyl-mcp

List Pterodactyl backups

ptero_list_backups

Read-onlyIdempotent

Lists a server's backups with UUID, size, status, lock state, and timestamps to identify a safe rollback point or verify whether a backup has finished.

Instructions

List a server's backups: uuid, name, size, whether each one completed successfully, whether it is locked against deletion, and its created/completed timestamps.

Use this to find a rollback point before or after a risky change, or to check whether a backup started with ptero_create_backup wait:false has finished yet (completed_at is null until it has). Call ptero_create_backup BEFORE any risky file write, delete, or power kill — this tool only reports what already exists, it does not take one for you.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`server`	No	Server short identifier (e.g. 1a2b3c4d). Omit to use PTERODACTYL_DEFAULT_SERVER. Call ptero_list_servers to discover valid identifiers.
`per_page`	No	Backups per page; the panel clamps this to 50. Omit for the panel default (20).

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of backups on this call (the panel does not paginate this list further here).
`server`	Yes
`backups`	Yes
`backup_count`	No	Count of non-failed backups, from the panel (meta.backup_count), when reported.
`backup_limit`	No	Maximum backups this server may hold at once, when the panel reports it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

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 and destructiveHint=false; description adds valuable semantics: completed_at is null until the backup finishes, and it only reports what exists. No contradiction between text and annotations, and the added detail goes beyond the structured hints.

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?

Three sentences each earn their place: the field list, the usage scenario, and the explicit clarification of scope. Slightly verbose but information-dense and front-loaded with the primary purpose.

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?

Output schema covers return structure, description covers usage and limitations, annotations cover safety. Nothing an agent needs to call it correctly is missing, including the pointer to ptero_create_backup as the complementary tool.

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 covers both parameters fully (server with default and discovery hint, per_page with clamp and default). Description adds no additional parameter info beyond what the schema already provides, so the baseline 3 applies.

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?

Clear verb 'list' with resource 'server backups', enumerates the fields returned (uuid, name, size, success, locked, timestamps), and stands apart from sibling tools like ptero_create_backup and ptero_delete_backup as a read-only reporting tool.

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 (finding rollback points before/after risky changes, checking async backup completion) and explicitly warns to call ptero_create_backup before risky operations, clarifying that this tool only reports existing backups and does not create one.

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