Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_view_comments

Read-onlyIdempotent

List comments from a legacy Chat view, ordered newest first. Retrieve message history with cursor-based pagination.

Instructions

List comments in a Chat view, newest first.

Calls GET /view/{view_id}/comment.

When to Use:

  • To read the message history of a legacy Chat-type view.

When NOT to Use:

  • To read messages in a modern Chat channel — use clickup_get_chat_channel_messages (tools/chat_messages.py) instead.

Returns: Markdown (default) or JSON list of comments with id, author, date, 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 = {"view_id": "105"}

Error Handling: 404 means the view id is wrong or is not a Chat-type view.

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?

Discloses return format (markdown/JSON), pagination details (cursor-based, same as clickup_get_task_comments), and error handling (404 for wrong/non-Chat view). No contradiction with annotations (readOnlyHint, etc.).

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 sections (When to Use, When NOT, Returns, Pagination, Examples, Error Handling). Front-loaded with the main purpose. No wasted words.

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?

Comprehensive for a tool with only one required parameter and an output schema. Covers pagination, error cases, and provides an example. No gaps.

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% but the description provides detailed pagination explanation and an example. While it doesn't reiterate parameter names, it adds value beyond the schema for understanding 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 the tool lists comments in a Chat view, newest first, and distinguishes it from sibling tools like clickup_get_chat_channel_messages for modern channels.

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 (legacy Chat views) and when not to use (modern Chat channels, directing to clickup_get_chat_channel_messages), giving clear alternatives.

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