Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-removeFromProject

Destructive

Removes a tag from a specified project using project ID and tag ID, letting you detach tags without deleting them from your Dokploy instance.

Instructions

POST /tag.removeFromProject

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

Input Schema

NameRequiredDescriptionDefault
tagIdYes
projectIdYes

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 already declare destructiveHint=true and openWorldHint=true, and the 'POST' in the description is consistent with a mutation. However, the description adds nothing beyond that: it does not say whether the tag itself survives, whether the operation is reversible, what permissions are needed, or what happens to already-unassigned tags.

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 only because it is under-specified rather than economical — a bare endpoint path is not a useful front-loaded summary of behavior. There is no structure beyond the verb and route.

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 two-parameter mutation with zero schema description coverage and no output schema, an agent needs context on target identity, side effects, and failure modes. The description supplies none of it.

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%, so both projectId and tagId are undocumented in structured fields, and the description does nothing to compensate. It does not state whether IDs are UUIDs, slugs, or names, nor whether they must reference existing assignments.

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 endpoint path 'POST /tag.removeFromProject', which essentially restates the tool name plus a verb. It conveys that a tag is detached from a project, but offers no scoping, no object identity, and no differentiation from siblings like tag-remove.

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 at all — no indication of how this differs from tag-remove (removing a tag entirely) or project-remove, and no preconditions or prerequisites. An agent must infer use cases purely from the name.

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