Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_threaded_comments

Read-onlyIdempotent

Retrieve all replies in a comment thread, excluding the parent comment. Use to read the full nested discussion under any comment.

Instructions

List the replies in a comment's thread.

Calls GET /comment/{comment_id}/reply. The parent comment itself is NOT included in the response — only its replies.

When to Use:

  • To read the full discussion nested under a specific comment.

When NOT to Use:

  • To read a task/list/Chat-view's top-level comments — use clickup_get_task_comments / clickup_get_list_comments / clickup_get_chat_view_comments.

Returns: Markdown (default) or JSON list of replies with id, author, date, and (truncated) text.

Pagination: Unlike the three top-level comment-listing tools, ClickUp does NOT expose start/start_id cursor pagination for replies — this endpoint returns the full thread in one call, so no cursor params are surfaced here.

Examples: params = {"comment_id": "446750"}

Error Handling: 404 means the parent comment_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 provide readOnlyHint and idempotentHint. The description adds details about response format (Markdown/JSON), fields (id, author, date, truncated text), pagination (full thread returned, no cursor), and error handling (404). No contradiction with 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-structured with clear sections, examples, bullet points, and no extraneous information. It is thorough yet concise.

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 simplicity (one required parameter, read-only), the description covers return values, pagination, error handling, and output format options. It is complete for effective use.

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

Parameters4/5

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

The input schema already describes comment_id and response_format with descriptions and default. The description adds an example (params = {'comment_id': '446750'}) and explains that response_format defaults to markdown, reinforcing parameter usage.

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 the replies in a comment's thread' and explicitly notes that the parent comment is not included. It distinguishes from sibling tools like clickup_get_task_comments by specifying when to use each.

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?

Includes dedicated 'When to Use' and 'When NOT to Use' sections, naming specific alternatives (clickup_get_task_comments, clickup_get_list_comments, clickup_get_chat_view_comments) for top-level comments.

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