Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

get_task_comments

Retrieve comments for a specific ClickUp task to view feedback, updates, or discussions related to task management.

Instructions

Get comments on a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID

Implementation Reference

  • MCP tool handler implementation for 'get_task_comments'. Resolves task ID using _resolve_task_id helper and delegates to ClickUpClient.get_task_comments, then formats the response.
    async def get_task_comments(self, task_id: str) -> Dict[str, Any]:
        """Get task comments."""
        try:
            # First resolve the task to get the internal ID
            task = await self._resolve_task_id(task_id)
            comments = await self.client.get_task_comments(task.id)
        except ClickUpAPIError as e:
            return {"error": f"Failed to get comments for task '{task_id}': {e!s}"}
    
        return {
            "task_id": task.id,
            "comments": [
                {
                    "id": comment["id"],
                    "text": comment["comment_text"],
                    "user": comment["user"]["username"],
                    "date": comment["date"],
                }
                for comment in comments
            ],
            "count": len(comments),
        }
  • Input schema definition for the get_task_comments tool, requiring task_id.
    Tool(
        name="get_task_comments",
        description="Get comments on a task",
        inputSchema={
            "type": "object",
            "properties": {
                "task_id": {"type": "string", "description": "Task ID"},
            },
            "required": ["task_id"],
        },
    ),
  • Registration of the get_task_comments handler in the tools dictionary mapping tool names to handler functions.
    self._tools: Dict[str, Callable] = {
        "create_task": self.create_task,
        "get_task": self.get_task,
        "update_task": self.update_task,
        "delete_task": self.delete_task,
        "list_tasks": self.list_tasks,
        "search_tasks": self.search_tasks,
        "get_subtasks": self.get_subtasks,
        "get_task_comments": self.get_task_comments,
        "create_task_comment": self.create_task_comment,
        "get_task_status": self.get_task_status,
        "update_task_status": self.update_task_status,
        "get_assignees": self.get_assignees,
        "assign_task": self.assign_task,
        "list_spaces": self.list_spaces,
        "list_folders": self.list_folders,
        "list_lists": self.list_lists,
        "find_list_by_name": self.find_list_by_name,
        # Bulk operations
        "bulk_update_tasks": self.bulk_update_tasks,
        "bulk_move_tasks": self.bulk_move_tasks,
        # Time tracking
        "get_time_tracked": self.get_time_tracked,
        "log_time": self.log_time,
        # Templates
        "create_task_from_template": self.create_task_from_template,
        "create_task_chain": self.create_task_chain,
        # Analytics
        "get_team_workload": self.get_team_workload,
        "get_task_analytics": self.get_task_analytics,
        # User management
        "list_users": self.list_users,
        "get_current_user": self.get_current_user,
        "find_user_by_name": self.find_user_by_name,
    }
  • Core API client handler that makes the HTTP request to ClickUp API to fetch task comments.
    async def get_task_comments(self, task_id: str) -> List[Dict[str, Any]]:
        """Get comments for a task."""
        data = await self._request("GET", f"/task/{task_id}/comment")
        return data.get("comments", [])
  • MCP server registration where tool definitions (including schemas) are provided via list_tools handler.
    @self.server.list_tools()
    async def list_tools() -> List[Tool]:
        """List all available tools."""
        return self.tools.get_tool_definitions()
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get comments' which implies a read-only operation, but doesn't disclose behavioral traits like whether it returns all comments, pagination, error handling, or authentication needs. This leaves significant gaps for an agent.

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 with a single sentence, 'Get comments on a task', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., comment list format, metadata) or any behavioral context, making it inadequate for a tool that likely involves data retrieval with potential complexities.

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 'task_id' clearly documented. The description adds no additional meaning beyond this, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get comments on a task' clearly states the action (get) and resource (comments on a task), which is adequate. However, it lacks specificity to distinguish it from siblings like 'create_task_comment' or other comment-related tools that might exist, making it somewhat vague in context.

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 is provided on when to use this tool versus alternatives. For example, it doesn't specify if this is for retrieving all comments, recent ones, or how it differs from 'get_task' which might include comments. Without such context, usage is unclear.

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