Skip to main content
Glama
MCP Dokploy Online
by igoruam

deployment-removeDeployment

Destructive

Deletes a deployment from a Dokploy instance by deployment ID, enabling cleanup of obsolete or failed deployments.

Instructions

POST /deployment.removeDeployment

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": {
      "deploymentId": "<deploymentId>"
    },
    "name": "deployment-removeDeployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
deploymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is carried by structured fields. The description adds no behavioral context whatsoever — not what gets deleted, whether dependent services or containers are torn down, whether it is irreversible, or what permissions are needed — which is a notable gap for a destructive operation. It does not contradict the annotations.

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 brief with no wasted words, but the brevity is under-specification rather than economy; the single route string carries essentially no informational payload. Nothing is front-loaded because there is no content to front-load.

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?

For a destructive single-parameter tool with no output schema and no parameter documentation, the description supplies nothing an agent needs to invoke it correctly: not the target's identity semantics, not the aftermath, not the error conditions. Completeness is effectively absent.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter deploymentId, so the description bears full responsibility for explaining it. It says nothing about the identifier's format, whether it is the deployment's own ID or a service/compose scoped ID, or how to obtain it, leaving the agent to guess.

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?

The description is only the HTTP route "POST /deployment.removeDeployment", which restates the tool name rather than stating what it does. It conveys that the operation is a POST targeting a deployment resource, but gives no scope, target, or effect, and does nothing to distinguish it from siblings such as application-dropDeployment or previewDeployment-delete.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no reference to alternatives. An agent must infer from the name alone that this removes a deployment and cannot tell from the definition how it differs from the several other deployment-termination tools in the catalog.

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