Skip to main content
Glama
yokan-board
by yokan-board

delete_task

Remove a task from a Yokan Kanban board by specifying the board ID and task ID to maintain organized workflows.

Instructions

Deletes a task from a board.

Args: board_id (int): The ID of the board containing the task. task_id (str): The ID of the task to delete. auth (AuthContext): The authentication context containing user ID and token.

Returns: None

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
task_idYes
authYes

Implementation Reference

  • The `delete_task` function, decorated with `@app_instance.tool`, implements the logic to remove a task from a board by ID and update the board data via `yokan_client`.
    async def delete_task(
        board_id: int,
        task_id: str,
        auth: AuthContext,
    ) -> None:
        """Deletes a task from a board.
    
        Args:
            board_id (int): The ID of the board containing the task.
            task_id (str): The ID of the task to delete.
            auth (AuthContext): The authentication context containing user ID and token.
    
        Returns:
            None
        """
        board = await yokan_client.get_board(board_id=board_id, token=auth.token)
        if "columns" not in board.data:
            raise McpError(error=ErrorData(code=NOT_FOUND, message="Task not found"))
    
        task_found = False
        for column in board.data["columns"].values():
            for i, task in enumerate(column.get("tasks", [])):
                if task.get("id") == task_id:
                    del column["tasks"][i]
                    task_found = True
                    break
            if task_found:
                break
    
        if not task_found:
            raise McpError(error=ErrorData(code=NOT_FOUND, message="Task not found"))
    
        await yokan_client.update_board(
            board_id=board_id, name=board.name, data=board.data, token=auth.token
        )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Deletes a task' which implies a destructive, irreversible mutation, but doesn't disclose behavioral traits like permissions needed (beyond auth param), confirmation prompts, cascading effects (e.g., if deletion affects other tasks), error handling, or rate limits. The description is minimal and lacks critical operational context for a destructive tool.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured clearly, though they could be more integrated. There's minimal waste, but the formatting as a docstring-like block slightly reduces readability compared to plain prose.

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?

Given the tool's complexity (destructive mutation with 3 params), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values (just 'None' without context), error conditions, side effects, or security implications. For a delete operation, this leaves significant gaps that could lead to misuse by 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 description coverage is 0%, so the description must compensate. It lists all three parameters with brief explanations: 'board_id' specifies the board containing the task, 'task_id' identifies the task to delete, and 'auth' provides authentication context. This adds basic meaning beyond the bare schema types, but doesn't detail format constraints (e.g., ID formats), validation rules, or how auth is used. It partially compensates for the coverage gap.

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 ('Deletes') and resource ('a task from a board'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_board' or 'delete_column' by specifying the target is a task, not a board or column. However, it doesn't explicitly differentiate from 'move_task' or 'update_task' in terms of destructive nature.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., task must exist), when-not-to-use scenarios (e.g., if task is in progress), or direct alternatives among siblings like 'move_task' for relocation instead of deletion. The agent must infer usage from the name alone.

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/yokan-board/yokan-board-mcp'

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