Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_task_comments

Read-onlyIdempotent

List comments from a task, newest first. Use to read discussion history before acting on the task.

Instructions

List comments on a task, newest first.

Calls GET /task/{task_id}/comment.

When to Use:

  • To read discussion history on a task before acting on it.

When NOT to Use:

  • To read replies inside a specific thread — use clickup_get_threaded_comments.

Returns: Markdown (default) or JSON list of comments with id, author, date, resolved state, assignee, and (truncated) text.

Pagination: Cursor-based, NOT limit/offset. Omit start/start_id for the most recent 25 comments (ClickUp's fixed page size — not configurable). To page to OLDER comments, pass the oldest comment's date as start and its id as start_id; the markdown output surfaces both values whenever a full page (25) comes back, so callers can loop until a short page signals the end.

Examples: params = {"task_id": "abc123"} params = {"task_id": "abc123", "start": 1508369194377, "start_id": "446750"}

Error Handling: 404 means the task id is wrong.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description significantly adds detailed behavioral context: it explains the return format (markdown or JSON), the fields included, and crucially, the cursor-based pagination mechanism with fixed page size, how to page older comments, and that the markdown output surfaces cursor values for looping. This goes well beyond the 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?

The description is well-organized with sections for purpose, API call, when to use/not, returns, pagination, examples, and error handling. Every sentence is informative and necessary. No redundancy or fluff. The structure aids quick comprehension.

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 (pagination, multiple optional parameters) and the presence of an output schema, the description covers all critical aspects: purpose, usage boundaries, return fields, pagination mechanics, error handling, and examples. It is fully sufficient for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite schema description coverage being 0% (per context signals), the description provides rich usage semantics for parameters. It explains how start and start_id work together for pagination, with examples and clear rules. It also mentions the response_format parameter indirectly by describing the output. This adds meaning beyond the input 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 'List comments on a task, newest first' and specifies the API call. It distinguishes itself from the sibling tool clickup_get_threaded_comments, which is for reading replies. The verb 'list' and resource 'comments on a task' are specific and 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?

The description includes explicit 'When to Use' and 'When NOT to Use' sections, directing agents to use this tool for reading discussion history and to use clickup_get_threaded_comments for threads. It also covers pagination and error handling, providing comprehensive usage 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