Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

create_task_comment

Add comments to ClickUp tasks to provide updates, instructions, or feedback, with options to assign users and notify team members.

Instructions

Create a comment on a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID
comment_textYesComment text
assigneeNoUser ID to assign (optional)
notify_allNoNotify all assignees (default: true)

Implementation Reference

  • MCP tool handler implementation for create_task_comment. Resolves the task ID using _resolve_task_id helper and delegates to ClickUpClient.create_task_comment.
    async def create_task_comment(
        self,
        task_id: str,
        comment_text: str,
        assignee: Optional[int] = None,
        notify_all: bool = True,
    ) -> Dict[str, Any]:
        """Create a comment on a task."""
        try:
            # First resolve the task to get the internal ID
            task = await self._resolve_task_id(task_id)
            comment_data = await self.client.create_task_comment(
                task.id, comment_text, assignee, notify_all
            )
        except ClickUpAPIError as e:
            return {"error": f"Failed to create comment on task '{task_id}': {e!s}"}
    
        return {
            "task_id": task.id,
            "comment_id": comment_data.get("id"),
            "comment_text": comment_text,
            "created": True,
            "notify_all": notify_all,
        }
  • JSON schema definition for the input parameters of the create_task_comment tool.
    Tool(
        name="create_task_comment",
        description="Create a comment on a task",
        inputSchema={
            "type": "object",
            "properties": {
                "task_id": {"type": "string", "description": "Task ID"},
                "comment_text": {"type": "string", "description": "Comment text"},
                "assignee": {
                    "type": "integer",
                    "description": "User ID to assign (optional)",
                },
                "notify_all": {
                    "type": "boolean",
                    "description": "Notify all assignees (default: true)",
                },
            },
            "required": ["task_id", "comment_text"],
        },
    ),
  • Registration of the create_task_comment handler in the tools dictionary within ClickUpTools.__init__.
    "get_task_comments": self.get_task_comments,
    "create_task_comment": self.create_task_comment,
  • ClickUpClient helper method that makes the actual API POST request to create a task comment.
    async def create_task_comment(
        self,
        task_id: str,
        comment_text: str,
        assignee: Optional[int] = None,
        notify_all: bool = True,
    ) -> Dict[str, Any]:
        """Create a comment on a task."""
        payload: Dict[str, Any] = {
            "comment_text": comment_text,
            "notify_all": notify_all,
        }
        if assignee:
            payload["assignee"] = assignee
    
        data = await self._request(
            "POST",
            f"/task/{task_id}/comment",
            json=payload,
        )
        return data
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a comment' implies a write/mutation operation, but the description doesn't address permissions needed, whether comments are editable/deletable, notification behavior (despite the 'notify_all' parameter), or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 extremely concise - a single sentence with no wasted words. It's front-loaded with the core purpose and contains no unnecessary elaboration. This is an example of efficient communication that respects the agent's processing constraints.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what constitutes a valid comment, how notifications work, what permissions are required, or what the tool returns. Given the complexity of creating a comment (which involves notifications, assignments, and task relationships), more context is needed for proper agent usage.

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 description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter context beyond what's in the schema (task_id, comment_text, optional assignee, notify_all default). This meets the baseline expectation when schema coverage is complete.

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 'Create a comment on a task' clearly states the action (create) and target resource (comment on a task). It's specific enough to understand the basic function, though it doesn't explicitly differentiate from sibling tools like 'get_task_comments' or explain what makes this operation unique beyond being a creation action.

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. There's no mention of prerequisites (e.g., needing an existing task), when to choose this over other comment-related operations, or any contextual constraints. The agent must infer usage from the tool name alone.

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

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