Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_list_comments

Read-onlyIdempotent

Retrieve comments on a list's info panel, sorted newest first. Use to read list-level discussion and status history.

Instructions

List comments on a List's info panel, newest first.

Calls GET /list/{list_id}/comment.

When to Use:

  • To read the List-level discussion/status history.

When NOT to Use:

  • To read comments on a specific task — use clickup_get_task_comments.

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

Pagination: Cursor-based (start/start_id), identical pattern to clickup_get_task_comments — see that tool's docstring for the full explanation. Omit both for the most recent 25 comments.

Examples: params = {"list_id": "901234"}

Error Handling: 404 means the list 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=true; description adds ordering (newest first), return format, pagination details (cursor-based, omit for recent 25), and error handling for 404. No contradictions.

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?

Well-structured with clear headings (When to Use, When NOT to Use, Returns, Pagination, Examples, Error Handling). Front-loaded with main purpose, concise and efficient.

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?

Covers purpose, usage, parameters, pagination, error handling. References sibling for full pagination explanation. Has output schema, so return values not needed. Complete for a read tool with good annotations.

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?

Schema coverage is 0%, so description must compensate. It explains list_id context, start/start_id usage via pagination section, and response_format via Returns. Adds meaning beyond 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 List's info panel, newest first.' It specifies the resource (List's info panel comments) and action (list), and differentiates from sibling clickup_get_task_comments.

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?

Explicitly provides 'When to Use' (read List-level discussion/status history) and 'When NOT to Use' (read task comments, use clickup_get_task_comments). Also references sibling for pagination pattern.

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