Skip to main content
Glama

clickup_chat_reply_list

Retrieve all threaded replies attached to a ClickUp chat message, ordered from oldest to newest. Provide the message ID to get the reply list.

Instructions

List the threaded replies attached to a top-level ClickUp Chat message, oldest first. Returns an array of reply objects. Use clickup_chat_reply_send to post a new reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYesID of the parent message. Obtain from clickup_chat_message_list (field: id).
team_idNoWorkspace (team) ID. Obtain from clickup_workspace_list (field: id). Omit to use the default workspace from config.
Behavior3/5

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

States ordering and basic output, but with no annotations, it does not disclose whether it's read-only, pagination behavior, or any side effects. Surficient but not thorough.

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?

Two concise sentences with no redundancy. Front-loaded with the main action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description only says 'Returns an array of reply objects' without detailing the structure of those objects. Leaves agent guessing about fields.

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

Parameters3/5

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

Schema descriptions already provide clear guidance on obtaining parameter values. The description does not add extra semantics beyond what is in the 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?

Clearly defines the tool as listing threaded replies to a top-level ClickUp Chat message, with ordering (oldest first) and return type. Distinguishes from sibling clickup_chat_reply_send.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions when to use the alternative tool (clickup_chat_reply_send) for posting. However, lacks explicit conditions for when not to use or prerequisites.

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/nicholasbester/clickup-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server