Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-clearDeployments

Idempotent

Clears all deployment records for a specified Dokploy application using its application ID, removing deployment history to reset the app's deploy state.

Instructions

POST /application.clearDeployments

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": {
      "applicationId": "<applicationId>"
    },
    "name": "application-clearDeployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations supply idempotentHint=true and openWorldHint=true, so the safety/behavior burden is partly covered by structured data. The description adds only the HTTP method, saying nothing about what state is destroyed, whether it is reversible, or what permissions are needed for a clear operation.

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; the single line conveys no information beyond what the name and annotations already state.

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?

This is a state-changing tool with no output schema and no annotation for destructiveness, yet the description explains neither effect, return value, nor error behavior. For a clear/destructive-style operation that is completely inadequate.

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?

Schema description coverage is 0% for the single required parameter applicationId, so the description must compensate and does not. It gives no indication of what the ID refers to, whether it is an application slug or numeric ID, or what happens when it is invalid.

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 'POST /application.clearDeployments', which restates the tool name plus an HTTP verb. It never says what 'clear' actually does (delete deployment records? drop all deployments? reset history?), so the agent cannot distinguish it from siblings such as application-dropDeployment, application-cancelDeployment, or compose-clearDeployments.

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 when-to-use guidance, no prerequisites, and no mention of any alternative. The many adjacent deployment tools (drop, cancel, killBuild, redeploy) are left entirely unaddressed, leaving the agent to guess which one is correct.

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