Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-remove

Destructive

Removes a tag from a Dokploy instance by tag ID, helping clean up unused or outdated tags in deployment and infrastructure management.

Instructions

POST /tag.remove

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": {
      "tagId": "<tagId>"
    },
    "name": "tag-remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description is not needed to establish that this is a destructive write. It nonetheless adds nothing beyond them: no statement about permanence, whether the tag is also detached from projects, or what happens to existing assignments.

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 with no wasted words, but that brevity is under-specification rather than conciseness. The single token carries no front-loaded statement of intent.

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 mutation with no output schema, undocumented parameters, and a near-identical sibling, the definition gives an agent almost nothing needed to invoke it safely or correctly.

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?

There is one required parameter, tagId, with 0% schema description coverage and no description text. The name is somewhat self-explanatory, but the definition provides no meaning beyond it, such as the ID format or whether an existing/assigned tag is required.

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 /tag.remove", which restates the tool name rather than explaining it. An agent must infer that it deletes a tag object entirely, and the presence of the sibling tag-removeFromProject makes that inference risky, since it is unclear whether this removes the tag itself or just an association.

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 or when-not-to-use guidance at all. Given the sibling tag-removeFromProject, the definition offers no help in choosing between removing a tag outright and detaching it from a project.

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