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

update_task

Modify task details in Yokan Board MCP by updating title, description, due date, or subtasks to keep project management current and organized.

Instructions

Updates the title, description, due date, and/or subtasks of an existing task.

Args: board_id (int): The ID of the board containing the task. task_id (str): The ID of the task to update. auth (AuthContext): The authentication context containing user ID and token. title (Optional[str], optional): The new title for the task. Defaults to None. description (Optional[str], optional): The new description for the task. Defaults to None. dueDate (Optional[str], optional): The new due date for the task (e.g., "YYYY-MM-DD"). Defaults to None. subtasks (Optional[List[str]], optional): A list of subtask IDs. Defaults to None.

Returns: None

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
task_idYes
authYes
titleNo
descriptionNo
dueDateNo
subtasksNo

Implementation Reference

  • The implementation of the `update_task` MCP tool, which updates task properties and calls `yokan_client.update_board` to persist changes.
    async def update_task(
        board_id: int,
        task_id: str,
        auth: AuthContext,
        title: Optional[str] = None,
        description: Optional[str] = None,
        dueDate: Optional[str] = None,
        subtasks: Optional[List[str]] = None,
    ) -> None:
        """Updates the title, description, due date, and/or subtasks of an existing task.
    
        Args:
            board_id (int): The ID of the board containing the task.
            task_id (str): The ID of the task to update.
            auth (AuthContext): The authentication context containing user ID and token.
            title (Optional[str], optional): The new title for the task. Defaults to None.
            description (Optional[str], optional): The new description for the task. Defaults to None.
            dueDate (Optional[str], optional): The new due date for the task (e.g., "YYYY-MM-DD"). Defaults to None.
            subtasks (Optional[List[str]], optional): A list of subtask IDs. Defaults to None.
    
        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 task in column.get("tasks", []):
                if task.get("id") == task_id:
                    if title is not None:
                        task["content"] = title
                    if description is not None:
                        task["description"] = description
                    if dueDate is not None:
                        task["dueDate"] = dueDate
                    if subtasks is not None:
                        task["subtasks"] = subtasks
                    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
        )
  • src/main.py:490-490 (registration)
    Registration of the `update_task` tool using the `@app_instance.tool` decorator.
    @app_instance.tool
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 this is an update operation but doesn't disclose behavioral traits like required permissions (implied by auth parameter but not explained), whether changes are reversible, what happens to unspecified fields, rate limits, or error conditions. The description adds minimal context beyond the basic 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 appropriately sized and front-loaded: the first sentence clearly states the purpose, followed by organized parameter and return sections. Every sentence earns its place, though the Returns section stating 'None' could be slightly more informative (e.g., 'Returns nothing on success').

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?

Given the complexity (mutation tool with 7 parameters, no annotations, no output schema), the description is moderately complete. It covers parameters well but lacks behavioral context (permissions, side effects) and output details. For a mutation tool, this leaves gaps an agent would need to infer or test.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates well by explaining all 7 parameters in the Args section, including their types, optionality, defaults, and examples (e.g., due date format 'YYYY-MM-DD'). It adds meaningful semantics beyond what the bare schema provides, though it doesn't explain the AuthContext structure in detail.

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 tool's purpose: 'Updates the title, description, due date, and/or subtasks of an existing task.' This specifies the verb (updates) and the resource (task) with the specific fields that can be modified. However, it doesn't distinguish this from sibling tools like 'update_board' or 'update_column' beyond mentioning it operates on tasks.

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., needing an existing task), exclusions, or comparisons to sibling tools like 'move_task' or 'create_task'. The agent must infer usage from the purpose statement 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