Skip to main content
Glama

update-task-comment

Modify the content or attachments of an existing comment on a Dooray task to update information or add files.

Instructions

Update an existing comment (댓글) on a Dooray task.

This tool modifies the content or attachments of an existing task comment.

IMPORTANT LIMITATION: Comments created from incoming emails CANNOT be modified. Only regular comments can be updated.

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId (if present)

  • Extract the second numeric ID (or the ID after "/tasks/") as taskId

  • Use get-task-comment-list to find the comment ID you want to update

REQUIRED: projectId, taskId, and commentId are all required.

Optional Parameters: You can provide either body, attachFileIds, or both. If you only want to update the text, just provide body. If you only want to update attachments, just provide attachFileIds.

File Attachments:

  • To attach files, first upload them using the file upload API

  • Then provide the returned file IDs in the attachFileIds parameter

  • See: https://helpdesk.dooray.com/share/pages/9wWo-xwiR66BO5LGshgVTg/2939987647631384419

Workflow:

  1. Use get-task-comment-list to find the comment you want to update and get its ID

  2. Call update-task-comment with the comment ID and new content/attachments

  3. The comment will be modified immediately

Content Format:

  • Use "text/x-markdown" for markdown formatting (recommended)

  • Use "text/html" for rich HTML content

  • Body format: {"mimeType": "text/x-markdown", "content": "..."}

Examples:

  • Update comment text only: { "projectId": "123456", "taskId": "789012", "commentId": "4219415732999317024", "body": { "mimeType": "text/x-markdown", "content": "## Updated Comment\n\nThis comment has been revised" } }

  • Update with new attachments: { "projectId": "123456", "taskId": "789012", "commentId": "4219415732999317024", "body": { "mimeType": "text/x-markdown", "content": "See updated files" }, "attachFileIds": ["file123", "file456"] }

Returns: Success message upon completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID where the task belongs
taskIdYesTask ID where the comment exists
commentIdYesComment ID to update
bodyNoNew comment content
attachFileIdsNoArray of file IDs to attach (optional)

Implementation Reference

  • The main handler function that executes the tool logic by calling the projects API to update the task comment and returns a success message or formatted error.
    export async function updateTaskCommentHandler(args: UpdateTaskCommentInput) {
      try {
        await projectsApi.updateTaskComment({
          projectId: args.projectId,
          taskId: args.taskId,
          commentId: args.commentId,
          body: args.body,
          attachFileIds: args.attachFileIds,
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully updated comment ${args.commentId}`
            }
          ],
        };
      } catch (error) {
        return formatError(error);
      }
    }
  • Zod schema definitions for input validation, including nested bodySchema and the main updateTaskCommentSchema used for tool parameter validation.
    const bodySchema = z.object({
      content: z.string().describe('Comment content'),
      mimeType: z.enum(['text/x-markdown', 'text/html']).describe('Content format (use text/x-markdown for most cases)'),
    });
    
    export const updateTaskCommentSchema = z.object({
      projectId: z.string().describe('Project ID where the task belongs'),
      taskId: z.string().describe('Task ID where the comment exists'),
      commentId: z.string().describe('Comment ID to update'),
      body: bodySchema.optional().describe('New comment content'),
      attachFileIds: z.array(z.string()).optional().describe('Array of file IDs to attach (optional)'),
    });
  • src/index.ts:56-56 (registration)
    Registers the updateTaskCommentHandler and updateTaskCommentSchema in the central toolRegistry map, which is used by the MCP server to dispatch tool calls.
    'update-task-comment': { handler: updateTaskCommentHandler, schema: updateTaskCommentSchema },
  • src/index.ts:79-79 (registration)
    Includes the updateTaskCommentTool definition in the tools array, which is returned in response to list_tools requests.
    updateTaskCommentTool,
  • Tool metadata object containing name, detailed description, and JSON inputSchema for the update-task-comment tool, used in list_tools responses.
    export const updateTaskCommentTool = {
      name: 'update-task-comment',
      description: `Update an existing comment (댓글) on a Dooray task.
    
    This tool modifies the content or attachments of an existing task comment.
    
    **IMPORTANT LIMITATION**: Comments created from incoming emails CANNOT be modified. Only regular comments can be updated.
    
    **URL Pattern Recognition**:
    When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":
    - Extract the first numeric ID after "/task/" as projectId (if present)
    - Extract the second numeric ID (or the ID after "/tasks/") as taskId
    - Use get-task-comment-list to find the comment ID you want to update
    
    **REQUIRED**: projectId, taskId, and commentId are all required.
    
    **Optional Parameters**: You can provide either body, attachFileIds, or both. If you only want to update the text, just provide body. If you only want to update attachments, just provide attachFileIds.
    
    **File Attachments**:
    - To attach files, first upload them using the file upload API
    - Then provide the returned file IDs in the attachFileIds parameter
    - See: https://helpdesk.dooray.com/share/pages/9wWo-xwiR66BO5LGshgVTg/2939987647631384419
    
    **Workflow**:
    1. Use get-task-comment-list to find the comment you want to update and get its ID
    2. Call update-task-comment with the comment ID and new content/attachments
    3. The comment will be modified immediately
    
    **Content Format**:
    - Use "text/x-markdown" for markdown formatting (recommended)
    - Use "text/html" for rich HTML content
    - Body format: {"mimeType": "text/x-markdown", "content": "..."}
    
    **Examples**:
    - Update comment text only: {
        "projectId": "123456",
        "taskId": "789012",
        "commentId": "4219415732999317024",
        "body": {
          "mimeType": "text/x-markdown",
          "content": "## Updated Comment\\n\\nThis comment has been revised"
        }
      }
    
    - Update with new attachments: {
        "projectId": "123456",
        "taskId": "789012",
        "commentId": "4219415732999317024",
        "body": {
          "mimeType": "text/x-markdown",
          "content": "See updated files"
        },
        "attachFileIds": ["file123", "file456"]
      }
    
    Returns: Success message upon completion.`,
      inputSchema: {
        type: 'object',
        properties: {
          projectId: {
            type: 'string',
            description: 'Project ID where the task belongs',
          },
          taskId: {
            type: 'string',
            description: 'Task ID where the comment exists',
          },
          commentId: {
            type: 'string',
            description: 'Comment ID to update',
          },
          body: {
            type: 'object',
            properties: {
              content: {
                type: 'string',
                description: 'Comment content',
              },
              mimeType: {
                type: 'string',
                enum: ['text/x-markdown', 'text/html'],
                description: 'Content format (use text/x-markdown for most cases)',
              },
            },
            required: ['content', 'mimeType'],
            description: 'New comment content',
          },
          attachFileIds: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Array of file IDs to attach (optional)',
          },
        },
        required: ['projectId', 'taskId', 'commentId'],
      },
    };
Behavior5/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 and does so comprehensively. It reveals critical behavioral traits: the 'IMPORTANT LIMITATION' about email comments, the immediate modification effect ('The comment will be modified immediately'), URL pattern recognition capabilities, authentication requirements (implied through file upload API reference), and the success message return. These go well beyond what the input schema provides.

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

Conciseness4/5

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

The description is well-structured with clear sections (limitation, URL pattern, parameters, workflow, format, examples) and front-loads the core purpose. While comprehensive, some sections like the detailed examples and external link could be slightly condensed. Every sentence adds value, but the length approaches the upper bound of appropriate conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with 5 parameters (including nested objects), no annotations, and no output schema, the description provides exceptional completeness. It covers purpose, limitations, prerequisites, parameter semantics, workflow, format details, examples, and return information. The only minor gap is not explicitly stating this is a write operation, but that's strongly implied by 'update' and 'modifies.'

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?

Schema description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema: it clarifies that projectId, taskId, and commentId are all 'REQUIRED' (reinforcing schema), explains the optional nature of body vs attachFileIds ('you can provide either... or both'), provides detailed content format guidance with mimeType enum context, and includes concrete examples showing parameter usage. This elevates the score above baseline.

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 specific action ('modifies the content or attachments'), resource ('existing task comment'), and distinguishes it from siblings like 'create-task-comment' (for creating new comments) and 'get-task-comment-list' (for listing comments). The opening sentence directly answers 'what does this tool do?'

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

Usage Guidelines5/5

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

Explicit guidance is provided on when to use this tool vs alternatives: 'Use get-task-comment-list to find the comment ID you want to update' (prerequisite), 'Comments created from incoming emails CANNOT be modified' (exclusion), and the workflow section outlines the complete usage sequence. The description clearly distinguishes this from creation and listing operations.

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/jhl8041/dooray-mcp'

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