Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_task_comment

Post a comment to a ClickUp task, optionally assigning an action item to a user or group, with notification support.

Instructions

Add a comment to a task.

Posts to POST /task/{task_id}/comment.

When to Use:

  • To leave feedback, ask a question, or hand off context on a task.

  • To assign a follow-up action item via assignee/group_assignee.

When NOT to Use:

  • To reply inside an existing comment thread — use clickup_create_threaded_comment.

  • To comment on a List's info panel or a Chat view — use clickup_create_list_comment / clickup_create_chat_view_comment.

Returns: A confirmation string with the new comment's id, hist_id, and timestamp, or an Error ... string on failure.

Examples: params = {"task_id": "abc123", "comment_text": "Blocked on design review.", "notify_all": True}

Error Handling: 404 means the task id is wrong; 403 can mean you lack comment access on the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds valuable behavioral context: return format (confirmation string with id, hist_id, timestamp) and error handling for 404/403. No contradiction with annotations.

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?

Well-structured with clear sections (purpose, endpoint, when to use, when not to use, returns, examples, error handling). Every sentence earns its place; no wasted words.

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 tool's complexity and the presence of annotations and schema, the description fully covers usage context, return values, error cases, and examples. It is complete for effective agent decision-making.

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 already provides descriptions for all parameters, so the tool description adds little beyond mentioning assignee/group_assignee for action items. With high schema coverage, a baseline of 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?

The description clearly states 'Add a comment to a task' and specifies the API endpoint. It distinguishes from sibling tools like clickup_create_threaded_comment and clickup_create_list_comment, making the purpose unambiguous.

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?

Explicitly lists when to use (feedback, questions, handoffs, action items) and when not to use (threaded replies, list/chat view comments), naming alternative tools. Provides excellent decision guidance.

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

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