Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_messages

Read-onlyIdempotent

List messages in a ClickUp Chat channel, sorted newest first, with cursor-based pagination. Retrieve author, timestamp, reply count, and content to read conversations or obtain message IDs for replies.

Instructions

List the messages in a Chat channel (newest first), cursor-paginated.

When to Use:

  • To read a channel's conversation, or to grab a message id before replying, reacting, updating, or deleting.

When NOT to Use:

  • To list channels themselves — use clickup_get_chat_channels (chat_channels).

  • To read one message's replies — use clickup_get_chat_message_replies.

Returns: Each message's author, id, timestamp, reply count, and a content snippet. When more results exist the output includes a next_cursor to page forward.

Pagination: Cursor-based. Call once, read next_cursor, then call again with cursor=<next_cursor> until it is empty.

Examples:

  • params = {"channel_id": "6-901..."}

  • params = {"channel_id": "6-901...", "cursor": "eyJ...", "limit": 100}

Error Handling: 404 → unknown channel id; 401 → bad token. Errors return an Error ... string.

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 indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral details: newest-first ordering, cursor-based pagination, return format (author, id, timestamp, reply count, content snippet), next_cursor handling, error codes (404, 401), and error output format.

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 (main action, When to Use/Not Use, Returns, Pagination, Examples, Error Handling). It is front-loaded with the core purpose, and every sentence adds unique value without redundancy.

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 presence of an output schema (so return values are documented elsewhere), the description provides comprehensive coverage: usage context, exclusions, pagination mechanics, concrete examples, and error handling, making it complete for correct invocation.

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 provides descriptions for all parameters (0% gap), baseline 3. The description adds practical context through examples and the pagination section, explaining how to use cursor and limit parameters, which elevates practical understanding.

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 messages in a Chat channel (newest first), cursor-paginated,' which is a specific verb+resource. It explicitly differentiates from siblings like clickup_get_chat_channels and clickup_get_chat_message_replies in the 'When NOT to Use' section.

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 both 'When to Use' and 'When NOT to Use' sections with specific alternative sibling tools, providing clear guidance on when to invoke this tool versus others.

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