Plane MCP Server

delete_work_item_comment

Deletes a specific comment from a work item in Plane by supplying project, work item, and comment IDs. Removes unwanted or outdated comments to keep discussions relevant.

Instructions

Delete a comment for a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item comment_id: UUID of the comment

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>",
      "work_item_id": "<work_item_id>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_work_item_comment"
  }
}

Input Schema

Name	Required	Description	Default
`comment_id`	Yes
`project_id`	Yes
`work_item_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Delete a comment' without explaining whether the delete is permanent, whether it cascades, what permissions are needed, or what happens if the comment does not exist. For a destructive operation, this lack of detail is a significant gap.

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: one sentence for the action plus a simple Args list. The verb is front-loaded, and there is no wasted wording. Every element contributes to understanding the tool's purpose and parameters.

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

Completeness3/5

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

The tool is simple (3 required string params, no output schema, no annotations), so the description covers the core usage. However, it omits any mention of return values, error behavior, or side effects (e.g., permanence). Given that no output schema exists, the description could have briefly noted what the agent should expect as a response, making it only minimally complete.

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

Parameters3/5

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

The input schema has no descriptions (0% coverage), so the description partially compensates by labeling each parameter as 'UUID of the project/work item/comment.' This adds basic format and purpose information beyond the raw schema, but it is minimal and largely restates what the parameter names suggest. It does not explain how to obtain these IDs or any relationships between them.

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 a comment for a work item.' The verb 'Delete' is specific, and the resource ('comment for a work item') is well-defined, distinguishing it from sibling tools like create_work_item_comment, update_work_item_comment, retrieve_work_item_comment, and list_work_item_comments.

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

Usage Guidelines3/5

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

The description implies use when deleting a comment, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. For example, it does not note that the comment must exist or that permissions are required. However, the operation is straightforward, so the intended usage is reasonably clear.

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

Deploy Server