Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_update_task

Modify an existing Todoist task by updating its content, description, due date, priority, or labels using the task ID.

Instructions

Update an existing task by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe ID of the task to update
contentNoNew content/title for the task (optional)
descriptionNoNew description for the task (optional)
dueStringNoNew due date in natural language (optional)
priorityNoNew priority level from 1 (normal) to 4 (urgent) (optional)
labelsNoNew array of label names (optional)

Implementation Reference

  • Handler logic for executing todoist_update_task: validates args with isUpdateTaskArgs, prepares updateData, calls todoistClient.updateTask(taskId, updateData), formats and returns response.
    if (name === "todoist_update_task") {
      if (!isUpdateTaskArgs(args)) {
        throw new Error("Invalid arguments for todoist_update_task");
      }
    
      const updateData: any = {};
      if (args.content) updateData.content = args.content;
      if (args.description) updateData.description = args.description;
      if (args.dueString) updateData.dueString = args.dueString;
      if (args.priority) updateData.priority = args.priority;
      if (args.labels) updateData.labels = args.labels;
    
      const updatedTask = await todoistClient.updateTask(args.taskId, updateData);
      
      return {
        content: [{ 
          type: "text", 
          text: `Task updated successfully:\nID: ${updatedTask.id}\n${formatTask(updatedTask)}` 
        }],
        isError: false,
      };
    }
  • Tool schema definition including name, description, and inputSchema for validating arguments to todoist_update_task.
    const UPDATE_TASK_TOOL: Tool = {
      name: "todoist_update_task",
      description: "Update an existing task by its ID",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The ID of the task to update"
          },
          content: {
            type: "string",
            description: "New content/title for the task (optional)"
          },
          description: {
            type: "string",
            description: "New description for the task (optional)"
          },
          dueString: {
            type: "string",
            description: "New due date in natural language (optional)"
          },
          priority: {
            type: "number",
            description: "New priority level from 1 (normal) to 4 (urgent) (optional)",
            enum: [1, 2, 3, 4]
          },
          labels: {
            type: "array",
            items: { type: "string" },
            description: "New array of label names (optional)"
          }
        },
        required: ["taskId"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of all tools including UPDATE_TASK_TOOL in the ListToolsRequestHandler, making todoist_update_task available.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        // Task tools
        CREATE_TASK_TOOL,
        QUICK_ADD_TASK_TOOL,
        GET_TASKS_TOOL,
        GET_TASK_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        COMPLETE_TASK_TOOL,
        REOPEN_TASK_TOOL,
        SEARCH_TASKS_TOOL,
        MOVE_TASK_TOOL,
        BULK_MOVE_TASKS_TOOL,
        // Project tools
        GET_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_PROJECT_TOOL,
        UPDATE_PROJECT_TOOL,
        DELETE_PROJECT_TOOL,
        // Section tools
        GET_SECTIONS_TOOL,
        CREATE_SECTION_TOOL,
        UPDATE_SECTION_TOOL,
        DELETE_SECTION_TOOL,
        // Label tools
        CREATE_LABEL_TOOL,
        GET_LABEL_TOOL,
        GET_LABELS_TOOL,
        UPDATE_LABEL_TOOL,
        DELETE_LABEL_TOOL,
        // Comment tools
        CREATE_COMMENT_TOOL,
        GET_COMMENT_TOOL,
        GET_COMMENTS_TOOL,
        UPDATE_COMMENT_TOOL,
        DELETE_COMMENT_TOOL,
      ],
    }));
  • Type guard helper function used to validate arguments for todoist_update_task before execution.
    function isUpdateTaskArgs(args: unknown): args is {
      taskId: string;
      content?: string;
      description?: string;
      dueString?: string;
      priority?: number;
      labels?: string[];
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "taskId" in args &&
        typeof (args as { taskId: string }).taskId === "string"
      );
    }
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 of behavioral disclosure. While 'Update' implies a mutation, the description doesn't specify required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields (e.g., if they remain unchanged). It lacks critical context 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 a single, efficient sentence that states the core purpose without waste. It's front-loaded and appropriately sized for a straightforward update operation, with every word 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like error conditions, response format, or side effects. Given the complexity of updating tasks with multiple optional fields, more context is needed to guide 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%, so the schema already documents all 6 parameters thoroughly. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain parameter interactions or provide examples). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Update') and resource ('an existing task'), making the purpose immediately understandable. It distinguishes from siblings like 'todoist_create_task' by specifying 'existing task', but doesn't differentiate from other update operations like 'todoist_update_comment' or 'todoist_update_project' beyond the resource type.

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 a valid task ID), when not to use it (e.g., for bulk updates), or alternatives like 'todoist_complete_task' for marking tasks as done. Usage is implied but not explicitly stated.

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/vitalio-sh/todoist-mcp-server-ext'

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