Skip to main content
Glama
goto-software

plane-mcp-server

delete_work_item

Remove a work item from a project by providing its UUID and the project's UUID. Use this to delete unwanted tasks or issues.

Instructions

Delete a work item by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
work_item_idYesUUID of the work item

Implementation Reference

  • The delete_work_item MCP tool handler function. It calls client.work_items.delete() to delete a work item by project_id and work_item_id.
    @mcp.tool()
    def delete_work_item(project_id: str, work_item_id: str) -> None:
        """
        Delete a work item by ID.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            work_item_id: UUID of the work item
        """
        client, workspace_slug = get_plane_client_context()
        client.work_items.delete(workspace_slug=workspace_slug, project_id=project_id, work_item_id=work_item_id)
  • The register_work_item_tools function which registers all work item tools (including delete_work_item) with the MCP server via @mcp.tool() decorator.
    def register_work_item_tools(mcp: FastMCP) -> None:
  • Import and call of register_work_item_tools(mcp) in the main tool registration orchestrator.
    from plane_mcp.tools.work_items import register_work_item_tools
    from plane_mcp.tools.work_logs import register_work_log_tools
    from plane_mcp.tools.workspaces import register_workspace_tools
    
    
    def register_tools(mcp: FastMCP) -> None:
        """Register all tools with the MCP server."""
        register_project_tools(mcp)
        register_work_item_tools(mcp)
  • Import of get_plane_client_context helper used by the handler to retrieve the Plane API client and workspace slug.
    from plane_mcp.client import get_plane_client_context
  • The inline type annotation (project_id: str, work_item_id: str) serves as the input schema for this tool. Returns None.
    @mcp.tool()
    def delete_work_item(project_id: str, work_item_id: str) -> None:
        """
        Delete a work item by ID.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            work_item_id: UUID of the work item
        """
        client, workspace_slug = get_plane_client_context()
        client.work_items.delete(workspace_slug=workspace_slug, project_id=project_id, work_item_id=work_item_id)
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action without revealing consequences (e.g., whether deletion is permanent, cascading effects on related items, or any required authorization). This is insufficient for a mutation operation.

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

Conciseness4/5

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

The description is extremely concise (6 words). It front-loads the essential action. However, it is so short that it misses useful information that a slightly longer description could provide without losing conciseness.

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?

With no output schema, the description does not explain what the tool returns (e.g., success status, deleted item details). For a simple delete operation, the description is adequate in purpose but lacks crucial information about the result and side effects, making it incomplete for an agent to fully understand the behavior.

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 already fully describes the two parameters with standard definitions (UUID fields). The description's 'by ID' adds no new meaning beyond what the schema provides. Schema coverage is 100%, so a baseline of 3 is appropriate.

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'), the resource ('work item'), and the method ('by ID'). This is specific and distinguishes it from other delete tools like 'delete_cycle' or 'delete_project' found among siblings.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or context like required permissions or whether the item must be unlinked from other entities. With many sibling delete tools, this lack of context could lead to incorrect invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/goto-software/plane-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server