Skip to main content
Glama
MCP Dokploy Online
by igoruam

previewDeployment-delete

Destructive

Deletes a preview deployment by ID to remove unused preview environments from Dokploy.

Instructions

POST /previewDeployment.delete

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": {
      "previewDeploymentId": "<previewDeploymentId>"
    },
    "name": "previewDeployment-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
previewDeploymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 covered structurally. The description adds nothing beyond that — no statement about permanence, cascading effects on associated deployments/domains, or whether confirmation is required, which is what a delete tool most needs to disclose.

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 shortness here reflects under-specification rather than conciseness. The only content is an endpoint string, with no front-loaded statement of what the tool does.

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 documented parameter needs the description to carry the burden of effect, irreversibility, and required identifier. None of that is present.

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%, so the description must explain previewDeploymentId but says nothing about its format, origin, or whether it comes from previewDeployment-all. The route text implies an identifier is passed but adds no usable meaning.

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 /previewDeployment.delete", which essentially restates the tool name. It implies removal of a preview deployment but never states the verb or object in prose, and gives no distinguishing detail versus siblings like previewDeployment-redeploy or application-dropDeployment.

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, when not to, or which sibling handles adjacent operations. An agent must infer everything from the name alone.

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