Skip to main content
Glama
MCP Dokploy Online
by igoruam

redirects-delete

Destructive

Deletes a redirect from Dokploy by its redirect ID. Use it to remove an existing redirect rule from your deployment configuration.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
redirectIdYes

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 known from structured data. The description adds nothing beyond that: no statement on whether deletion is permanent, whether dependent resources are affected, or what the response contains.

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?

The single line is short but that brevity reflects under-specification rather than efficiency; there is no front-loaded statement of purpose or effect. Nothing is wasted, but almost nothing is present.

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 delete operation with an undocumented parameter and no output schema, the definition provides no behavioral or procedural context at all. The only useful information an agent has comes from the annotations and schema, not the description.

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 parameter redirectId, so the description would need to explain its format and source. It says nothing, leaving only the parameter name itself to convey 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 just the HTTP route 'POST /redirects.delete', which restates the tool name rather than explaining what is deleted. An agent can infer a redirect record is removed, but there is no statement of effect, scope, or how this differs from sibling tools such as redirects-update or redirects-one.

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 alternatives or when deletion should be avoided. The only content is the endpoint path, leaving the agent to guess the operational context 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