Skip to main content
Glama
goto-software

plane-mcp-server

delete_cycle

Delete a specific cycle from a project by providing the project and cycle UUIDs.

Instructions

Delete a cycle by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
cycle_idYesUUID of the cycle

Implementation Reference

  • The delete_cycle function that executes the tool logic. It retrieves the Plane client context and calls client.cycles.delete() with the workspace_slug, project_id, and cycle_id.
    @mcp.tool()
    def delete_cycle(project_id: str, cycle_id: str) -> None:
        """
        Delete a cycle by ID.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            cycle_id: UUID of the cycle
        """
        client, workspace_slug = get_plane_client_context()
        client.cycles.delete(workspace_slug=workspace_slug, project_id=project_id, cycle_id=cycle_id)
  • The register_cycle_tools function registers all cycle-related tools (including delete_cycle) via the @mcp.tool() decorator on the FastMCP server instance.
    def register_cycle_tools(mcp: FastMCP) -> None:
        """Register all cycle-related tools with the MCP server."""
  • Import of register_cycle_tools from the cycles module into the tools package.
    from plane_mcp.tools.cycles import register_cycle_tools
  • Invocation of register_cycle_tools(mcp) to register all cycle tools including delete_cycle with the MCP server.
    register_cycle_tools(mcp)
  • Test reference to delete_cycle in the integration test file, confirming the tool is listed among the expected cycle tools.
    "delete_cycle",
Behavior2/5

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

No annotations provided; description only says 'Delete' without disclosing side effects, permissions, reversibility, or impact on associated work items. Full burden on description, which fails to provide behavioral context.

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?

Single sentence is concise but lacks structure. It earns its place, but could be more informative with brief notes on usage or behavior.

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 destructive operation with no annotations and no output schema, the description is insufficient. Does not clarify if deletion is hard or soft, or whether associated items are affected.

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?

Input schema has 100% coverage with explicit descriptions for both parameters (UUIDs). Description adds no additional meaning beyond what schema already provides, warranting baseline score.

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?

Description clearly states the action 'Delete', the resource 'cycle', and the identification method 'by ID'. This is specific and distinct from sibling tools like archive_cycle which may not permanently delete.

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 on when to use this tool versus alternatives (e.g., archive_cycle for soft delete). No mention of prerequisites or context for deletion.

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