Skip to main content
Glama
MCP Dokploy Online
by igoruam

domain-delete

Destructive

Deletes a domain from a Dokploy instance using its domain ID, removing the associated domain configuration from the server.

Instructions

POST /domain.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": {
      "domainId": "<domainId>"
    },
    "name": "domain-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes

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 agent knows this is a destructive, externally-visible operation. The description adds nothing beyond that: no disclosure of what gets removed (DNS records, certificates, linked services), whether deletion is reversible, or whether confirmation/authorization is required.

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 short because it is under-specified rather than efficient – a bare route string that conveys no actionable information. Nothing is front-loaded because there is no substantive content to order.

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 mutation with no output schema and no parameter documentation, the description is wholly inadequate. An agent cannot tell what will be destroyed, what will happen to dependent resources, or how to confirm success.

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% and the description says nothing about the single required parameter, domainId. The parameter name is largely self-explanatory (a domain identifier, string), which keeps this above the floor, but no format, source, or lookup guidance is provided.

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 'POST /domain.delete', which merely restates the tool name and HTTP route. It does convey a delete operation on a domain resource, but that is fully derivable from the name 'domain-delete' and adds no scope, target, or differentiating detail versus siblings like domain-update or domain-toggleEnable.

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 or preconditions (e.g. whether services must be moved off the domain first), and no mention of alternatives. An agent must guess entirely.

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