Skip to main content
Glama

create_threaded_comment

Add a threaded reply to an existing comment in ClickUp, with the option to notify all assignees.

Instructions

Create a new threaded comment (reply) to a parent comment. Supports notification settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesThe ID of the parent comment
comment_textYesThe text content of the comment
notify_allNoWhether to notify all assignees

Implementation Reference

  • Registration of the 'create_threaded_comment' MCP tool using server.tool(), with Zod schema input validation (comment_id, comment_text, notify_all) and handler that delegates to commentsClient.createThreadedComment.
    // Register create_threaded_comment tool
    server.tool(
      'create_threaded_comment',
      'Create a new threaded comment (reply) to a parent comment. Supports notification settings.',
      {
        comment_id: z.string().describe('The ID of the parent comment'),
        comment_text: z.string().describe('The text content of the comment'),
        notify_all: z.boolean().optional().describe('Whether to notify all assignees')
      },
      async ({ comment_id, ...commentParams }) => {
        try {
          const result = await commentsClient.createThreadedComment(comment_id, commentParams as CreateThreadedCommentParams);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating threaded comment:', error);
          return {
            content: [{ type: 'text', text: `Error creating threaded comment: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The createThreadedComment method on the CommentsClient class that makes the actual API call via this.client.post('/comment/{commentId}/reply', params).
    /**
     * Create a new threaded comment on a parent comment
     * @param commentId The ID of the parent comment
     * @param params The comment parameters
     * @returns The created threaded comment
     */
    async createThreadedComment(commentId: string, params: CreateThreadedCommentParams): Promise<Comment> {
      return this.client.post(`/comment/${commentId}/reply`, params);
    }
  • The CreateThreadedCommentParams interface defining the input shape: comment_text (string) and notify_all (optional boolean).
    export interface CreateThreadedCommentParams {
      comment_text: string;
      notify_all?: boolean;
    }
  • src/index.ts:40-47 (registration)
    The setupTools method in the ClickUpServer class that calls setupCommentTools(this.server), indirectly registering the create_threaded_comment tool.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It mentions creating a reply and notification settings but omits permissions, side effects, error conditions, or required parent existence. This is insufficient for safe invocation.

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 two short, focused sentences with no unnecessary words. It is front-loaded with the core action and additional detail in the second sentence.

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 no annotations or output schema, the description is too sparse. It does not cover return values, constraints (e.g., character limits), or edge cases like invalid parent_id. For a creation tool, this is inadequate.

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 coverage is 100%, so schema already documents all parameters. The description adds minimal context by noting 'reply' and 'notification settings', but does not significantly enhance parameter understanding beyond the schema.

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 explicitly states 'Create a new threaded comment (reply) to a parent comment', which is a specific verb+resource. It distinguishes from sibling tools like create_task_comment or create_list_comment by focusing on threaded replies.

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

Usage Guidelines3/5

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

The description implies usage for replying to a parent comment but provides no explicit when-to-use or alternatives. The sibling set includes many comment-related tools, yet no guidance on selection is given.

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