Skip to main content
Glama

update_comment

Modify an existing ClickUp comment by updating its text, reassigning it, or marking it as resolved.

Instructions

Update an existing ClickUp comment's properties including text, assignee, and resolved status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesThe ID of the comment to update
comment_textYesThe new text content of the comment
assigneeNoThe ID of the user to assign to the comment
resolvedNoWhether the comment is resolved

Implementation Reference

  • Registration of the 'update_comment' tool on the MCP server with its Zod schema (comment_id, comment_text, assignee, resolved) and handler that delegates to commentsClient.updateComment.
    // Register update_comment tool
    server.tool(
      'update_comment',
      'Update an existing ClickUp comment\'s properties including text, assignee, and resolved status.',
      {
        comment_id: z.string().describe('The ID of the comment to update'),
        comment_text: z.string().describe('The new text content of the comment'),
        assignee: z.number().optional().describe('The ID of the user to assign to the comment'),
        resolved: z.boolean().optional().describe('Whether the comment is resolved')
      },
      async ({ comment_id, ...commentParams }) => {
        try {
          const result = await commentsClient.updateComment(comment_id, commentParams as UpdateCommentParams);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating comment:', error);
          return {
            content: [{ type: 'text', text: `Error updating comment: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Handler function for the 'update_comment' tool. It calls commentsClient.updateComment(comment_id, commentParams) and returns the result as JSON, or an error message on failure.
    async ({ comment_id, ...commentParams }) => {
      try {
        const result = await commentsClient.updateComment(comment_id, commentParams as UpdateCommentParams);
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
        };
      } catch (error: any) {
        console.error('Error updating comment:', error);
        return {
          content: [{ type: 'text', text: `Error updating comment: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'update_comment' tool: requires comment_id (string) and comment_text (string), optional assignee (number) and resolved (boolean).
    {
      comment_id: z.string().describe('The ID of the comment to update'),
      comment_text: z.string().describe('The new text content of the comment'),
      assignee: z.number().optional().describe('The ID of the user to assign to the comment'),
      resolved: z.boolean().optional().describe('Whether the comment is resolved')
    },
  • The CommentsClient.updateComment method that sends a PUT request to /comment/{commentId} with the provided params.
    async updateComment(commentId: string, params: UpdateCommentParams): Promise<Comment> {
      return this.client.put(`/comment/${commentId}`, params);
    }
  • The UpdateCommentParams TypeScript interface defining the shape: comment_text (string), assignee (optional number), resolved (optional boolean).
    export interface UpdateCommentParams {
      comment_text: string;
      assignee?: number;
      resolved?: boolean;
    }
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. Only says 'update properties' without mentioning side effects, idempotency, or error conditions (e.g., comment not found).

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?

Single sentence, 12 words, no fluff. Front-loaded with verb and resource. Efficient.

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?

Tool is simple with 4 parameters; description covers basic purpose. However, lacks details on return value or error handling, and no output schema provided. Adequate but incomplete for autonomous agent 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 has 100% coverage for all 4 parameters. Description merely summarizes three of them, adding no additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

Description clearly states verb 'update', resource 'comment', and specific properties (text, assignee, resolved status). It is explicit and distinguishes from sibling tools like create, delete, and get.

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?

No guidance on when to use this tool versus alternatives such as create or delete comment. No context provided for prerequisites or conditions.

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/nsxdavid/clickup-mcp-server'

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