Skip to main content
Glama

uncomplete_task

Reopen a completed Todoist task by providing its ID to restore it to active status for continued management.

Instructions

Uncomplete (reopen) a task by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to uncomplete

Implementation Reference

  • The handler function for the 'uncomplete_task' MCP tool. It calls the uncompleteTask service function with the provided task_id and returns a success or error message.
    handler: async (args: { task_id: string }) => {
      try {
        await uncompleteTask(args.task_id);
        return {
          content: [
            {
              type: 'text',
              text: 'Task uncompleted successfully',
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${
                error instanceof Error ? error.message : 'Unknown error'
              }`,
            },
          ],
        };
      }
    },
  • The schema definition for the 'uncomplete_task' tool, specifying the name, description, and input schema requiring task_id.
    schema: {
      name: 'uncomplete_task',
      description: 'Uncomplete (reopen) a task by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          task_id: {
            type: 'string',
            description: 'The ID of the task to uncomplete',
          },
        },
        required: ['task_id'],
      },
    },
  • The core helper function uncompleteTask that uses the Todoist client to reopen (uncomplete) the task via the /reopen API endpoint.
    export async function uncompleteTask(taskId: string): Promise<void> {
      const client = getTodoistClient();
    
      try {
        await client.post!(`/tasks/${taskId}/reopen`);
      } catch (error) {
        throw new Error(`Failed to uncomplete task: ${getErrorMessage(error)}`);
      }
    }
  • src/index.ts:98-99 (registration)
    Registration of the uncompleteTaskTool.schema in the MCP server's ListTools response.
    completeTaskTool.schema,
    uncompleteTaskTool.schema,
  • Registration of the uncomplete_task handler in the toolsWithArgs dispatch registry for handling tool calls.
    complete_task: completeTaskTool.handler,
    uncomplete_task: uncompleteTaskTool.handler,
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation (reopening) but doesn't disclose permissions needed, whether the operation is reversible, error conditions (e.g., invalid ID), or side effects. The phrase 'uncomplete (reopen)' suggests it changes task status, but lacks details on what 'reopen' entails practically.

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 extremely concise and front-loaded in a single, efficient sentence. Every word earns its place by specifying the action and target, with no redundant or vague phrasing.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'reopen' means behaviorally (e.g., sets status to incomplete, updates timestamps), what the tool returns, or error handling. Given the complexity of task management and rich sibling tools, more context is needed for effective use.

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 100%, with the single parameter 'task_id' clearly documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, such as ID format or validation rules. Baseline 3 is appropriate since the schema fully covers the parameter.

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 ('uncomplete/reopen') and resource ('a task by its ID'), making the purpose immediately understandable. It distinguishes itself from 'complete_task' by specifying the opposite operation, though it doesn't explicitly mention sibling tools like 'update_task' which might also modify task status.

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 be completed first), compare to sibling tools like 'update_task' for status changes, or specify contexts where reopening is appropriate versus creating a new task.

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/bkotos/todoist-mcp'

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