Skip to main content
Glama

clickup

by io.usefulapi

Create task comment

clickup_create_task_comment
Destructive

WRITE: add a comment to a task. comment_text is required; the task is the {task_id} path param. ClickUp REST: POST /task/{task_id}/comment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task id to comment on (path param, not body).
assigneeNoUser id to assign the comment to (numeric).
notify_allNoIf true, notify everyone tagged/subscribed (else just the assignee).
comment_textYesThe comment text (required).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description says 'WRITE: add a comment', which is consistent. The description adds the REST endpoint but does not disclose side effects, idempotency, or permissions. No contradiction exists.

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, focused sentence that is front-loaded with the operation type and clearly presents the key information. It is concise with no unnecessary filler.

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

Completeness4/5

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

Given the tool's simplicity, full schema coverage, and annotations, the description is sufficient for an agent to invoke it correctly. It lacks return-value details, but no output schema exists, and the core purpose is well covered.

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 parameters are fully documented. The description repeats that comment_text is required and task_id is a path param without adding additional semantic meaning beyond the schema.

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' with a specific verb and resource. It distinguishes itself from sibling tools like create_task (creating tasks) and get_task_comments (reading comments).

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

Usage Guidelines4/5

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

The 'WRITE:' prefix and 'add a comment' clearly imply when to use this tool (write context) as opposed to read-only siblings. However, it does not explicitly name alternatives or state when-not-to-use, so it falls short of a 5.

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

All clickup toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a unique resource+action combination, with clear scoping (e.g., get_tasks vs search_tasks differ by list vs workspace, list_lists vs list_folderless_lists by parent). No two tools appear to do the same thing, and the descriptions make boundaries explicit.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, search_, update_+resource), prefixed with clickup_. No camelCase or unconventional verbs are present.

Tool Count5/5

14 tools is a well-scoped size for a project management API, covering hierarchy traversal (workspaces, spaces, folders, lists), task operations, comments, and user info. Each tool serves a clear purpose without unnecessary bloat.

Completeness4/5

The surface covers core CRUD for tasks (create, read, update) and comments, plus full hierarchy listing and search. Minor gaps include no delete task/comment and no update/list operations for folders/lists, but these are workable and don't hinder the primary workflows.

Resources