Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-remove

Destructive

Permanently deletes a specified Dokploy backup by its backup ID. Use it to remove outdated or unwanted backups and keep your deployment storage clean.

Instructions

POST /backup.remove

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "backupId": "<backupId>"
    },
    "name": "backup-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description adds nothing on top: it does not say the deletion is irreversible, what data is destroyed, whether dependent resources are affected, or what authorization is required. For a destructive mutation this is a serious gap.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than conciseness; a raw endpoint stub carries no front-loaded information an agent can act on.

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

Completeness1/5

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

A destructive, single-parameter tool with no output schema and no annotation detail beyond destructiveHint needs the description to explain effect and prerequisites. Nothing is covered.

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

Parameters1/5

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

There is one required parameter (backupId) with 0% schema description coverage, and the description offers no meaning for it — no format, no source of the ID, no example. The description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /backup.remove" restates the tool name and HTTP method without describing the resource in prose or distinguishing it from siblings like backup-create, backup-update, or backup-one. An agent can infer it deletes a backup only by decoding the dotted path.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, no prerequisites, no exclusions, and no mention of alternatives such as backup-listBackupFiles for inspecting backups before removal.

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