Plane MCP Server

manage_release_labels

Attach or detach existing palette labels to a release by providing the release ID, action (attach/detach), and label IDs. Returns the updated label set.

Instructions

Attach or detach existing palette labels on a release. Use list_release_labels with release_id to read.

Args: release_id: UUID of the release action: "attach" to add the labels, "detach" to remove them label_ids: UUIDs of palette labels to attach/detach

Returns: The release's attached labels after the operation

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": {
      "release_id": "<release_id>",
      "action": "<action>",
      "label_ids": "<label_ids>"
    },
    "name": "manage_release_labels"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`label_ids`	Yes
`release_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation and its return value ('The release's attached labels after the operation'), but does not disclose potential failure modes, idempotency, or behavior when detaching non-attached labels. This is adequate but not rich.

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 concise and well-structured: a one-sentence summary, a helpful pointer to the read tool, then structured Args and Returns sections. Every sentence contributes valuable information without redundancy.

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 tool's simplicity and the presence of an output schema, the description is largely complete. It covers all parameters, the action semantics, and the return value, while also distinguishing from the read sibling tool. It could be slightly more comprehensive about edge cases, but overall satisfies the needs for this simple tool.

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?

All three parameters are explicitly described in the description with types and semantics: release_id as UUID, action with enumerated values, and label_ids as UUIDs of palette labels. This fully compensates for the 0% schema description coverage, adding meaning beyond the raw schema fields.

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 opens with 'Attach or detach existing palette labels on a release,' a specific verb and resource combination that clearly states the tool's function. It distinguishes itself from siblings like list_release_labels, create_release_label, and delete_release_label by focusing on the attachment/detachment operation on existing labels.

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

Usage Guidelines4/5

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

The description explicitly directs users to 'Use list_release_labels with release_id to read,' providing an alternative for read operations and implying this tool is for modifications. It clearly explains the two actions (attach/detach), though it doesn't explicitly mention that creating new labels should be done via create_release_label.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server