Skip to main content
Glama

create_task_comment

Add comments to Todoist tasks to provide context, updates, or instructions. This tool enables users to annotate tasks with additional information through Claude Desktop.

Instructions

Create a new comment on a specific Todoist task. The comment will automatically include a signature indicating it was created using Claude.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to add a comment to
contentYesThe content of the comment to add

Implementation Reference

  • The handler function that executes the create_task_comment tool logic, invoking the service function and returning structured JSON response.
      handler: async (args: { task_id: string; content: string }) => {
        try {
          const comment = await createTaskComment(args.task_id, args.content);
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(
                  {
                    success: true,
                    message: 'Comment created successfully',
                    comment: {
                      id: comment.id,
                      content: comment.content,
                      posted: comment.posted,
                      posted_uid: comment.posted_uid,
                      attachment: comment.attachment,
                    },
                  },
                  null,
                  2
                ),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(
                  {
                    success: false,
                    message: 'Failed to create comment',
                    error: error instanceof Error ? error.message : 'Unknown error',
                  },
                  null,
                  2
                ),
              },
            ],
          };
        }
      },
    };
  • The schema definition for the create_task_comment tool, including name, description, and input schema.
    schema: {
      name: 'create_task_comment',
      description:
        'Create a new comment on a specific Todoist task. The comment will automatically include a signature indicating it was created using Claude.',
      inputSchema: {
        type: 'object',
        properties: {
          task_id: {
            type: 'string',
            description: 'The ID of the task to add a comment to',
          },
          content: {
            type: 'string',
            description: 'The content of the comment to add',
          },
        },
        required: ['task_id', 'content'],
      },
    },
  • Registration of the create_task_comment handler in the toolsWithArgs registry used by handleToolRequest.
    const toolsWithArgs: Record<string, (args: any) => Promise<ToolResponse>> = {
      get_task_comments: getTaskCommentsTool.handler,
      create_project_label: createProjectLabelTool.handler,
      create_task_comment: createTaskCommentTool.handler,
      update_task: updateTaskTool.handler,
      create_task: createTaskTool.handler,
      move_task: moveTaskTool.handler,
      get_tasks_with_label: getTasksWithLabelTool.handler,
      complete_task: completeTaskTool.handler,
      uncomplete_task: uncompleteTaskTool.handler,
      search_tasks: searchTasksTool.handler,
      search_tasks_using_and: searchTasksUsingAndTool.handler,
      search_tasks_using_or: searchTasksUsingOrTool.handler,
      complete_becky_task: completeBeckyTaskTool.handler,
    };
  • The service helper function that creates a Todoist task comment with an appended Claude signature, delegating to createCommentInternal.
    export async function createTaskComment(
      taskId: string,
      content: string
    ): Promise<CommentResult> {
      try {
        const commentContent = `${content}\n\n*(commented using Claude)*`;
        return await createCommentInternal(taskId, commentContent);
      } catch (error) {
        throw new Error(`Failed to create task comment: ${getErrorMessage(error)}`);
      }
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a write operation ('Create') and mentions the automatic signature addition, which is useful behavioral context. However, it doesn't cover important aspects like authentication requirements, error conditions, rate limits, or what happens if the task ID is invalid.

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 perfectly concise - a single sentence that states exactly what the tool does with no wasted words. It's front-loaded with the core functionality and includes the important behavioral detail about the automatic signature.

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?

For a write operation with no annotations and no output schema, the description is somewhat incomplete. It covers the basic action and one behavioral trait (signature), but lacks information about return values, error handling, and operational constraints that would be important for an agent to use this tool effectively.

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 documentation, so the description doesn't need to add parameter semantics. The description doesn't provide any additional parameter information beyond what's in the schema, which is acceptable given the comprehensive schema coverage.

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 ('Create a new comment') and target resource ('on a specific Todoist task'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'get_task_comments' beyond the obvious create vs. get distinction, so it doesn't fully address potential confusion with related operations.

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, or how it relates to sibling tools like 'get_task_comments' or 'update_task' for comment management.

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