Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_update_comment

Modify existing Todoist comments by providing a comment ID and new content to update task or project annotations.

Instructions

Update an existing comment by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentIdYesThe ID of the comment to update
contentYesNew content/text for the comment

Implementation Reference

  • The main handler logic for the 'todoist_update_comment' tool within the CallToolRequestSchema handler. Validates arguments using isUpdateCommentArgs, calls todoistClient.updateComment(commentId, updateArgs), formats the response using formatComment, and handles errors.
    if (name === "todoist_update_comment") {
      if (!isUpdateCommentArgs(args)) {
        return { content: [{ type: "text", text: "Invalid arguments for update_comment" }], isError: true };
      }
      try {
        const { commentId, ...updateArgs } = args;
        const updatedComment = await todoistClient.updateComment(commentId, updateArgs);
        return { 
          content: [{ type: "text", text: `Comment updated:\n${formatComment(updatedComment)}` }], 
          isError: false 
        };
      } catch (error: any) {
        return { content: [{ type: "text", text: `Error updating comment: ${error.message}` }], isError: true };
      }
    }
  • The Tool object definition including name, description, and inputSchema (JSON Schema) for validating arguments: requires commentId and content.
    const UPDATE_COMMENT_TOOL: Tool = {
      name: "todoist_update_comment",
      description: "Update an existing comment by its ID",
      inputSchema: {
        type: "object",
        properties: {
          commentId: {
            type: "string",
            description: "The ID of the comment to update"
          },
          content: {
            type: "string",
            description: "New content/text for the comment"
          }
        },
        required: ["commentId", "content"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of the tool in the ListToolsRequestSchema handler. UPDATE_COMMENT_TOOL is included in the array of available tools returned by the server.
    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 function used by the handler to validate input arguments match the expected shape: {commentId: string, content: string}.
    function isUpdateCommentArgs(args: unknown): args is {
      commentId: string;
      content: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "commentId" in args &&
        "content" in args &&
        typeof (args as { commentId: string; content: string }).commentId === "string" &&
        typeof (args as { commentId: string; content: string }).content === "string"
      );
    }
  • Helper function to format the comment object into a human-readable string for the tool response.
    function formatComment(comment: any): string {
      let commentDetails = `- ID: ${comment.id}\n  Content: ${comment.content}`;
      if (comment.postedAt) commentDetails += `\n  Posted At: ${comment.postedAt}`;
      if (comment.taskId) commentDetails += `\n  Task ID: ${comment.taskId}`;
      if (comment.projectId) commentDetails += `\n  Project ID: ${comment.projectId}`;
      if (comment.attachment) {
        commentDetails += `\n  Attachment: ${comment.attachment.fileName || 'File'} (${comment.attachment.fileType})`;
        if (comment.attachment.fileUrl) commentDetails += `\n  File URL: ${comment.attachment.fileUrl}`;
      }
      return commentDetails;
    }
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. It states 'Update an existing comment by its ID,' which implies a mutation operation but doesn't cover permissions needed, rate limits, whether the update is reversible, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate, scoring a 2 for minimal transparency.

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, direct sentence: 'Update an existing comment by its ID.' It is front-loaded with the core action and resource, with zero wasted words. This is optimally concise and well-structured, earning a 5.

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 operation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral aspects like side effects, error handling, or return values. For a tool that modifies data, this minimal description is insufficient, scoring a 2 for significant gaps in context.

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?

The input schema has 100% description coverage, with clear parameter definitions (commentId and content). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. According to the rules, with high schema coverage (>80%), the baseline is 3, so this scores a 3 for adequate but no extra value.

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 ('Update') and target resource ('an existing comment'), which is specific and unambiguous. It distinguishes from siblings like todoist_create_comment (create) and todoist_delete_comment (delete), though it doesn't explicitly contrast with todoist_get_comment (read) beyond the verb difference. This earns a 4 for clear purpose with some sibling differentiation.

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 comment ID), exclusions, or comparisons to siblings like todoist_create_comment for new comments or todoist_get_comment for viewing. With only a basic statement of function, this scores a 2 for lacking usage context.

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