Skip to main content
Glama
goto-software

plane-mcp-server

by goto-software
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delete_epic

Delete a specific epic by providing its project and epic UUIDs.

Instructions

Delete an epic by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
epic_idYesUUID of the epic

Implementation Reference

  • plane_mcp/tools/epics.py:264-285 (handler)
    The delete_epic MCP tool handler. It takes project_id and epic_id, gets the Plane client context, and calls client.work_items.delete() with the epic_id as the work_item_id.
    @mcp.tool()
def delete_epic(
    project_id: str,
    epic_id: str,
) -> None:
    """
    Delete an epic by ID.

    Args:
        project_id: UUID of the project
        epic_id: UUID of the epic

    Returns:
        None
    """
    client, workspace_slug = get_plane_client_context()

    return client.work_items.delete(
        workspace_slug=workspace_slug,
        project_id=project_id,
        work_item_id=epic_id,
    )
  • plane_mcp/tools/epics.py:19-19 (registration)
    The registration function that registers all epic tools (including delete_epic) with the MCP server via the @mcp.tool() decorator.
    def register_epic_tools(mcp: FastMCP) -> None:
  • plane_mcp/tools/__init__.py:47-48 (registration)
    The top-level registration call that invokes register_epic_tools from the tools __init__.py.
    register_epic_tools(mcp)
register_milestone_tools(mcp)

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

The description simply says 'Delete', which implies a destructive operation, but it does not disclose side effects (e.g., cascading deletes, irreversibility, permission requirements). No annotations are provided to fill this gap.

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

Conciseness3/5

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

The description is very concise (one sentence) but lacks informative content. It is not necessarily wasteful, but it omits important behavioral details, so it does not fully earn its place.

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?

For a delete tool, the description should mention irreversibility or dependencies (e.g., work items under the epic). It only states the basic operation, leaving significant gaps for an agent.

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?

Schema coverage is 100% and the description adds no extra meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate as the schema already documents both parameters adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (delete) and resource (epic) and specifies by ID, making the basic purpose clear. However, it does not distinguish itself from other delete tools like delete_cycle, delete_initiative, etc., but the tool name already differentiates by resource type.

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 vs alternatives (e.g., retrieve_epic, update_epic). It lacks context about prerequisites or when deletion is appropriate.

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