Skip to main content
Glama
Sign In
ClickUp MCP Sedrver

ClickUp MCP Sedrver

by nsxdavid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_chat_view_comment

Create a comment in a ClickUp chat view and optionally notify all assignees.

Instructions

Create a new comment in a ClickUp chat view. Supports 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": {
      "view_id": "<view_id>",
      "comment_text": "<comment_text>"
    },
    "name": "create_chat_view_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
view_idYesThe ID of the chat view to comment on
comment_textYesThe text content of the comment
notify_allNoWhether to notify all assignees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only mentions 'supports notification settings', but fails to address side effects, permissions, or any consequences (e.g., triggers notifications, requires write access). The description is too minimal to provide adequate transparency.

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 a single sentence that conveys the core action and a key feature (notification settings). No unnecessary words, front-loaded with purpose.

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?

Given the tool has 3 parameters and no output schema or annotations, the description provides basic completeness but lacks details on return behavior, error states, or prerequisites. It meets minimal requirements but is not comprehensive.

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 covers all parameters (100%). The description adds no specific parameter details beyond the schema; 'supports notification settings' loosely hints at notify_all but doesn't clarify its effect. Baseline 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 the action ('Create a new comment') and the resource ('ClickUp chat view'), and distinguishes from sibling tools like create_task_comment or create_list_comment by specifying the context. The mention of notification settings adds useful scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for creating comments in chat views, but does not explicitly state when to use it versus alternatives (e.g., use create_task_comment for task comments). There is no guidance on when not to use it or prerequisites.

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