Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_label

Remove a label from a Plane project by providing the project ID and label ID. Use this to clean up or manage labels in your project.

Instructions

Delete a label by ID.

Args: project_id: UUID of the project label_id: UUID of the label

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": {
      "project_id": "<project_id>",
      "label_id": "<label_id>"
    },
    "name": "delete_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Delete a label by ID' without mentioning the irreversible nature, potential cascade effects on associated work items, permission requirements, or any side effects. This is insufficient for a destructive operation.

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, with a single action sentence and a clear parameter list. Every word serves a purpose with no unnecessary detail.

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

Completeness2/5

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

This is a mutation tool with no annotations and no output schema. The description provides no information about return behavior, errors, idempotency, or consequences of deletion. For a destructive operation, this is incomplete.

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

Parameters4/5

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

Although the schema has 0% description coverage, the description explicitly explains both parameters: project_id as 'UUID of the project' and label_id as 'UUID of the label'. This adds meaningful context beyond the raw schema, clarifying the role of each parameter.

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 'Delete a label by ID' with the specific resource (label) and action (delete). It distinguishes itself from sibling tools like create_label, update_label, retrieve_label, and list_labels by indicating the destructive operation.

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 simply states what the tool does but provides no guidance on when to use it versus alternatives, no prerequisites, and no exclusions. For example, it doesn't mention whether the label must exist or if deleting a label has implications for work items using it.

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