ClickUp MCP Sedrver

create_list_comment

Post a comment to a ClickUp list, optionally assigning a user and notifying all assignees.

Instructions

Create a new comment on a ClickUp list. 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": {
      "list_id": "<list_id>",
      "comment_text": "<comment_text>"
    },
    "name": "create_list_comment"
  }
}

Input Schema

Name	Required	Description
`list_id`	Yes	The ID of the list to comment on
`comment_text`	Yes	The text content of the comment
`assignee`	No	The ID of the user to assign to the comment
`notify_all`	No	Whether to notify all assignees

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0May 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. While 'Create' implies mutation, it does not mention authentication needs, rate limits, side effects, or return values. The description adds minimal behavioral context beyond the input schema.

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, front-loaded with the core purpose and a brief mention of optional features. Every word earns its place; no unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple create operation with no output schema, the description covers the basic function. However, it lacks context about return values, error handling, or typical usage patterns relative to sibling tools. It is adequate but not rich.

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 the baseline is 3. The description summarizes parameters ('optional assignee and notification settings') but does not add meaning beyond the schema's own descriptions. No new semantic information is provided.

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 the action ('Create'), the resource ('new comment on a ClickUp list'), and hints at optional features. It effectively distinguishes from sibling tools like create_task_comment by specifying 'list'.

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 such as create_task_comment or create_chat_view_comment. The description only states what the tool does without exclusions or context.

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