Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_release_tag

Delete a release tag by its unique ID. Provide the tag_id (UUID) to remove unwanted release tags from your Plane project, simplifying release version management.

Instructions

Delete a release tag by ID.

Args: tag_id: UUID of the release tag

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": {
      "tag_id": "<tag_id>"
    },
    "name": "delete_release_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tag_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the verb 'delete' – no mention of permissions, irreversibility, side effects, or response behavior. This leaves the agent to infer from the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single sentence plus a parameter annotation. It front-loads the purpose and then provides the parameter detail. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one parameter, no output schema), the description covers the essential action and parameter semantics. It does not discuss edge cases like not-found behavior or permanence, but for a straightforward delete, this is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines tag_id as a required string with no description. The description compensates by specifying 'UUID of the release tag', giving the agent the format and semantic meaning of the parameter. This is exactly the kind of compensation needed for 0% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (delete) and resource (release tag) with the identifying mechanism (by ID). This distinguishes it from sibling tools like delete_release or delete_release_label.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or contexts. It does not mislead, but it offers no usage direction.

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