Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_message_replies

Read-onlyIdempotent

Retrieve threaded replies for a specific chat message, with cursor-based pagination for managing large threads.

Instructions

List the replies threaded under a Chat message, cursor-paginated.

When to Use:

  • To read a thread hanging off a specific message.

When NOT to Use:

  • To list top-level channel messages — use clickup_get_chat_messages.

Returns: Each reply's author, id, timestamp, and content snippet, plus a next_cursor when more replies exist.

Pagination: Cursor-based (see clickup_get_chat_messages).

Examples:

  • params = {"message_id": "abc123"}

  • params = {"message_id": "abc123", "cursor": "eyJ..."}

Error Handling: 404 → unknown message id. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds cursor-based pagination details, error handling (404), and response structure (author, id, timestamp, content snippet, next_cursor), going beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (When to Use, When NOT to Use, Returns, Pagination, Examples, Error Handling). It is concise but includes necessary context without extraneous fluff.

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 complexity (multiple parameters, pagination) and the presence of an output schema, the description covers key aspects: purpose, usage, pagination, error handling, and basic return fields. However, it omits details about the limit parameter and response format options, which are left to the schema.

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

Parameters2/5

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

The description does not describe each parameter individually; only message_id and cursor are mentioned in examples. With 0% schema description coverage from the description, it fails to add meaning beyond the existing input schema descriptions for less obvious parameters like workspace_id, content_format, and response_format.

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 replies threaded under a chat message with cursor pagination. It explicitly distinguishes from siblings by noting that for top-level messages, use clickup_get_chat_messages.

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 'When to Use' and 'When NOT to Use' sections provide explicit guidance. It says when to read a thread and when to use an alternative tool for top-level messages.

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