Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_reopen_task

Reopen a Todoist task by marking it as incomplete using the task ID. Restores tasks that were previously completed for better task management and organization.

Instructions

Reopen a task in Todoist (i.e., mark the task as incomplete)

Args: task_id: ID of the task to reopen

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • The handler function todoist_uncomplete_task implements the logic to reopen (uncomplete) a Todoist task using the Todoist API. This matches the functionality of 'todoist_reopen_task'.
    def todoist_uncomplete_task(ctx: Context, task_id: str) -> str:
        """Reopen a task in Todoist (i.e., mark the task as incomplete)
    
        Args:
            task_id: ID of the task to reopen
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Reopening task with ID: {task_id}")
    
            try:
                task = todoist_client.get_task(task_id=task_id)
                task_content = task.content
            except Exception as error:
                logger.warning(f"Error getting task with ID: {task_id}: {error}")
                return f"Could not verify task with ID: {task_id}. Task reopening aborted."
    
            is_success = todoist_client.uncomplete_task(task_id=task_id)
    
            logger.info(f"Task reopened successfully: {task_id}")
            return f"Successfully reopened task: {task_content} (ID: {task_id})"
        except Exception as error:
            logger.error(f"Error reopening task: {error}")
            return f"Error reopening task: {str(error)}"
  • src/main.py:90-90 (registration)
    Registers the todoist_uncomplete_task (reopen task handler) as an MCP tool.
    mcp.tool()(todoist_uncomplete_task)
  • src/main.py:26-36 (registration)
    Imports the todoist_uncomplete_task function from tasks.py for registration.
    from .tasks import (
        todoist_get_task,
        todoist_get_tasks,
        todoist_filter_tasks,
        todoist_add_task,
        todoist_update_task,
        todoist_complete_task,
        todoist_uncomplete_task,
        todoist_move_task,
        todoist_delete_task,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('reopen') but does not disclose behavioral traits such as required permissions, whether this affects task history or due dates, error conditions (e.g., if the task is already open), or what the response looks like. This is a significant gap for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, and the 'Args' section efficiently documents the parameter. There is zero waste, with every sentence earning its place.

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 (a mutation with no annotations, 1 parameter, and no output schema), the description is incomplete. It lacks details on behavioral aspects like permissions, side effects, error handling, and return values, which are crucial for an AI agent to invoke it correctly.

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?

The description adds meaning beyond the input schema by explaining that 'task_id' is the 'ID of the task to reopen', which clarifies the parameter's purpose. With 0% schema description coverage and only 1 parameter, this adequately compensates, though it could specify format (e.g., numeric vs. string).

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 ('reopen') and resource ('a task in Todoist'), with the parenthetical explanation 'mark the task as incomplete' providing precise meaning. It effectively distinguishes from sibling tools like 'todoist_close_task' (which does the opposite) and 'todoist_update_task' (which might modify other fields).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for marking incomplete tasks, but does not explicitly state when to use this versus alternatives like 'todoist_update_task' with a status field or 'todoist_create_task' for new tasks. It provides clear context by specifying the action, but lacks explicit exclusions or named alternatives.

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

Related 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/mikemc/todoist-mcp-server'

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