Skip to main content
Glama
goto-software

plane-mcp-server

delete_work_log

Remove a specific work log entry from a work item by providing project, work item, and log IDs.

Instructions

Delete a work log for a work item.

Input Schema

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

Implementation Reference

  • The delete_work_log function (handler) that executes the tool logic. It is decorated with @mcp.tool(), takes project_id, work_item_id, and work_log_id as parameters, gets the Plane client context, and calls client.work_items.work_logs.delete() to delete the work log.
    @mcp.tool()
    def delete_work_log(
        project_id: str,
        work_item_id: str,
        work_log_id: str,
    ) -> None:
        """
        Delete a work log for a work item.
    
        Args:
            project_id: UUID of the project
            work_item_id: UUID of the work item
            work_log_id: UUID of the work log
        """
        client, workspace_slug = get_plane_client_context()
        client.work_items.work_logs.delete(
            workspace_slug=workspace_slug,
            project_id=project_id,
            work_item_id=work_item_id,
            work_log_id=work_log_id,
        )
  • The registration chain: register_tools() calls register_work_log_tools(mcp) which registers all work log tools (including delete_work_log) with the MCP server via the @mcp.tool() decorator.
    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)
        register_user_tools(mcp)
        register_module_tools(mcp)
        register_initiative_tools(mcp)
        register_intake_tools(mcp)
        register_label_tools(mcp)
        register_page_tools(mcp)
        register_work_item_property_tools(mcp)
        register_work_item_type_tools(mcp)
        register_state_tools(mcp)
        register_workspace_tools(mcp)
        register_epic_tools(mcp)
        register_milestone_tools(mcp)
  • The register_work_log_tools function that registers all work log tools with the MCP server. delete_work_log is defined inside this function with the @mcp.tool() decorator.
    def register_work_log_tools(mcp: FastMCP) -> None:
        """Register all work log-related tools with the MCP server."""
    
        @mcp.tool()
        def list_work_logs(
            project_id: str,
            work_item_id: str,
            params: dict[str, Any] | None = None,
        ) -> list[WorkItemWorkLog]:
            """
            List work logs for a work item.
    
            Args:
                project_id: UUID of the project
                work_item_id: UUID of the work item
                params: Optional query parameters as a dictionary
    
            Returns:
                List of WorkItemWorkLog objects
            """
            client, workspace_slug = get_plane_client_context()
            return client.work_items.work_logs.list(
                workspace_slug=workspace_slug,
                project_id=project_id,
                work_item_id=work_item_id,
                params=params,
            )
    
        @mcp.tool()
        def create_work_log(
            project_id: str,
            work_item_id: str,
            duration: int | None = None,
            description: str | None = None,
        ) -> WorkItemWorkLog:
            """
            Create a work log for a work item.
    
            Args:
                project_id: UUID of the project
                work_item_id: UUID of the work item
                duration: Duration of work in minutes
                description: Description of the work performed
    
            Returns:
                Created WorkItemWorkLog object
            """
            client, workspace_slug = get_plane_client_context()
    
            data: dict[str, Any] = {}
            if duration is not None:
                data["duration"] = duration
            if description is not None:
                data["description"] = description
    
            return client.work_items.work_logs.create(
                workspace_slug=workspace_slug,
                project_id=project_id,
                work_item_id=work_item_id,
                data=data,
            )
    
        @mcp.tool()
        def update_work_log(
            project_id: str,
            work_item_id: str,
            work_log_id: str,
            duration: int | None = None,
            description: str | None = None,
        ) -> WorkItemWorkLog:
            """
            Update a work log for a work item.
    
            Args:
                project_id: UUID of the project
                work_item_id: UUID of the work item
                work_log_id: UUID of the work log
                duration: Duration of work in minutes
                description: Description of the work performed
    
            Returns:
                Updated WorkItemWorkLog object
            """
            client, workspace_slug = get_plane_client_context()
    
            data: dict[str, Any] = {}
            if duration is not None:
                data["duration"] = duration
            if description is not None:
                data["description"] = description
    
            return client.work_items.work_logs.update(
                workspace_slug=workspace_slug,
                project_id=project_id,
                work_item_id=work_item_id,
                work_log_id=work_log_id,
                data=data,
            )
    
        @mcp.tool()
        def delete_work_log(
            project_id: str,
            work_item_id: str,
            work_log_id: str,
        ) -> None:
            """
            Delete a work log for a work item.
    
            Args:
                project_id: UUID of the project
                work_item_id: UUID of the work item
                work_log_id: UUID of the work log
            """
            client, workspace_slug = get_plane_client_context()
            client.work_items.work_logs.delete(
                workspace_slug=workspace_slug,
                project_id=project_id,
                work_item_id=work_item_id,
                work_log_id=work_log_id,
            )
  • The file imports: FastMCP, WorkItemWorkLog model, and get_plane_client_context helper which is used by delete_work_log to obtain the client and workspace_slug.
    """Work log-related tools for Plane MCP Server."""
    
    from typing import Any
    
    from fastmcp import FastMCP
    from plane.models.work_items import WorkItemWorkLog
    
    from plane_mcp.client import get_plane_client_context
    
    
    def register_work_log_tools(mcp: FastMCP) -> None:
        """Register all work log-related tools with the MCP server."""
    
        @mcp.tool()
        def list_work_logs(
            project_id: str,
            work_item_id: str,
            params: dict[str, Any] | None = None,
        ) -> list[WorkItemWorkLog]:
            """
  • The import statement that brings register_work_log_tools into the tools package's __init__.py.
    from plane_mcp.tools.work_logs import register_work_log_tools
Behavior2/5

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

With no annotations, the description carries full burden but only states the action 'delete'. It does not disclose behavioral traits such as data permanence, authorization requirements, or side effects (e.g., cascading deletions), which are critical 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 a single, efficient sentence. It is appropriately concise for a simple delete operation, though it could include a bit more context without losing brevity.

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 straightforward delete tool, the description lacks completeness. It omits any mention of return value (typically a success/error indication), prerequisites (e.g., existence of work log), or behavioral nuances like idempotency.

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 provides 100% description coverage for all three UUID parameters. The description adds no extra meaning beyond the schema, so a baseline score 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 verb 'Delete' and the resource 'work log for a work item', making the tool's purpose unambiguous. It is specific and distinguishes it from sibling delete tools that target different resources.

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 like create_work_log or update_work_log. There is no discussion of prerequisites, context, or exclusions, leaving the agent without decision support.

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