Skip to main content
Glama
goto-software

plane-mcp-server

remove_work_item_from_cycle

Remove a specified work item from a cycle to manage project scope and scheduling.

Instructions

Remove a work item from a cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
cycle_idYesUUID of the cycle
work_item_idYesUUID of the work item to remove

Implementation Reference

  • The handler function for the 'remove_work_item_from_cycle' tool. Decorated with @mcp.tool(), it removes a work item from a cycle by calling the Plane client's cycles.remove_work_item method with workspace_slug, project_id, cycle_id, and work_item_id.
    @mcp.tool()
    def remove_work_item_from_cycle(
        project_id: str,
        cycle_id: str,
        work_item_id: str,
    ) -> None:
        """
        Remove a work item from a cycle.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            cycle_id: UUID of the cycle
            work_item_id: UUID of the work item to remove
        """
        client, workspace_slug = get_plane_client_context()
        client.cycles.remove_work_item(
            workspace_slug=workspace_slug,
            project_id=project_id,
            cycle_id=cycle_id,
            work_item_id=work_item_id,
        )
  • The tool is registered via the @mcp.tool() decorator inside the register_cycle_tools function, which is called from plane_mcp/tools/__init__.py's register_tools() function.
    @mcp.tool()
    def remove_work_item_from_cycle(
        project_id: str,
        cycle_id: str,
        work_item_id: str,
    ) -> None:
        """
        Remove a work item from a cycle.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            cycle_id: UUID of the cycle
            work_item_id: UUID of the work item to remove
        """
        client, workspace_slug = get_plane_client_context()
        client.cycles.remove_work_item(
            workspace_slug=workspace_slug,
            project_id=project_id,
            cycle_id=cycle_id,
            work_item_id=work_item_id,
        )
  • Top-level registration: register_cycle_tools(mcp) is called from register_tools(), which registers all cycle tools including remove_work_item_from_cycle.
    def register_tools(mcp: FastMCP) -> None:
        """Register all tools with the MCP server."""
        register_project_tools(mcp)
        register_work_item_tools(mcp)
        register_work_item_activity_tools(mcp)
        register_work_item_comment_tools(mcp)
        register_work_item_link_tools(mcp)
        register_work_item_relation_tools(mcp)
        register_work_log_tools(mcp)
        register_cycle_tools(mcp)
  • Helper function get_plane_client_context() that provides the Plane client instance and workspace_slug used by the handler to make the API call.
    def get_plane_client_context() -> PlaneClientContext:
        """
        Initialize and return a PlaneClient instance with workspace context.
    
        Authentication is handled by the PlaneOAuthProvider, which supports:
        1. Environment variables (PLANE_API_KEY + PLANE_WORKSPACE_SLUG)
        2. HTTP headers (x-api-key + x-workspace-slug)
        3. OAuth access token
    
        Environment variables:
        - PLANE_INTERNAL_BASE_URL: Internal URL for Plane API (preferred for server-to-server calls)
        - PLANE_BASE_URL: Base URL for Plane API (fallback, default: https://api.plane.so)
    
        Returns:
            PlaneClientContext containing configured PlaneClient instance and workspace slug
    
        Raises:
            ConfigurationError: If access token is not available or workspace slug is missing
        """
        base_url = os.getenv("PLANE_INTERNAL_BASE_URL") or os.getenv("PLANE_BASE_URL", "https://api.plane.so")
        workspace_slug = os.getenv("PLANE_WORKSPACE_SLUG", "")
    
        api_key = os.getenv("PLANE_API_KEY", "")
        access_token = None
    
        # Get access token from the OAuth provider (which handles all auth methods)
        stored_access_token: AccessToken | None = get_access_token()
        if stored_access_token:
            # Determine authentication method to use appropriate PlaneClient constructor
            auth_method = stored_access_token.claims.get("auth_method", "oauth")
            token = stored_access_token.token
            workspace_slug = stored_access_token.claims.get("workspace_slug", "")
    
            # For API key auth methods, use api_key parameter; for OAuth, use access_token
            if auth_method in ("api_key_env", "api_key_header"):
                api_key = token
            else:
                access_token = token
    
        if access_token:
            client = PlaneClient(
                base_url=base_url,
                access_token=access_token,
            )
        else:
            client = PlaneClient(
                base_url=base_url,
                api_key=api_key,
            )
    
        return PlaneClientContext(
            client=client,
            workspace_slug=workspace_slug,
        )
Behavior2/5

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

No annotations provided; description only says 'Remove,' failing to disclose side effects, permissions needed, or whether the removal is reversible.

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?

One concise sentence with no redundancy, though slightly minimal given the complexity of removal operations.

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?

Adequate for a simple removal with three UUID parameters, but lacks information about return value or success confirmation.

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 covers all three parameters with UUID descriptions; description adds no extra meaning beyond what the schema provides, so baseline 3.

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 verb 'Remove' and the resource 'a work item from a cycle,' differentiating it from sibling tools like add_work_items_to_cycle or remove_work_item_from_module.

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., remove_work_item_from_module) or prerequisites (e.g., work item must be in the cycle).

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