Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_work_item_property_value

Remove all values of a custom property from a work item. Specify project, work item, and property IDs to clear the property.

Instructions

Delete the value(s) of a custom property on a work item.

For multi-value properties, deletes all values for that property.

Args: project_id: UUID of the project work_item_id: UUID of the work item property_id: UUID of the work item property

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>",
      "property_id": "<property_id>"
    },
    "name": "delete_work_item_property_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
property_idYes
work_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that multi-value properties will have ALL values deleted, which is a non-obvious behavioral trait beyond what the tool name suggests. However, it does not address reversibility, permissions, or what happens when no value exists, leaving some gaps.

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?

Two sentences plus a three-line args list. The purpose is front-loaded, the multi-value edge case is a single sentence, and the parameter documentation is compact. No filler.

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?

Three simple params, no annotations, and no output schema. The description covers purpose, the multi-value behavior, and all parameter roles, which is adequate for a straightforward deletion tool. It does not describe success/failure responses, but given the tool's simplicity, this is a minor gap.

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?

Schema description coverage is 0%, and the description compensates by listing each argument with a clarifying role ('UUID of the project,' 'UUID of the work item,' 'UUID of the work item property'). This adds meaning beyond the bare string type in the schema, though it mostly expands on what the parameter names already suggest.

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 uses a specific verb ('Delete') with a clear resource ('the value(s) of a custom property on a work item'), and correctly distinguishes itself from sibling tools like delete_work_item_property (which removes the property definition itself) and set_work_item_property_value (which sets values). The multi-value clarification further sharpens the scope.

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 when to use the tool (to remove property values from a work item) but provides no explicit guidance on when NOT to use it or which alternative to choose. With many sibling tools like set_work_item_property_value, delete_work_item_property, and get_work_item_property_value, explicit differentiation would be valuable.

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