Skip to main content
Glama
Sign In
ClickUp MCP Sedrver

ClickUp MCP Sedrver

by nsxdavid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_task_comment

Add a comment to a ClickUp task with optional user assignment and notification settings.

Instructions

Create a new comment on a ClickUp task. Supports optional assignee and notification settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "comment_text": "<comment_text>"
    },
    "name": "create_task_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task to comment on
comment_textYesThe text content of the comment
assigneeNoThe ID of the user to assign to the comment
notify_allNoWhether to notify all assignees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the operation (create) and optional parameters, but omits important details such as return value, authentication requirements, or side effects (e.g., does it trigger notifications?).

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?

Two sentences, no redundant words. The key information (action, resource, optional features) is front-loaded and concise.

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?

With 4 parameters, no output schema, and no annotations, the description is insufficient for safe invocation. It lacks information about return format, error conditions, or required permissions, leaving gaps for the agent.

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?

Input schema provides 100% coverage with descriptions for each parameter. The description adds context that assignee and notify_all are optional 'settings', but this does not significantly enhance understanding beyond the schema.

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 clearly states it creates a comment on a ClickUp task, which distinguishes it from sibling tools like create_chat_view_comment or create_list_comment. However, it does not explicitly call out the differentiation.

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 like create_threaded_comment or create_list_comment. It does not mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools