Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_message_reactions

Read-onlyIdempotent

Retrieve emoji reactions on a chat message, including the user who added each reaction. Supports cursor-based pagination.

Instructions

List the emoji reactions on a Chat message, cursor-paginated.

When to Use:

  • To see who reacted to a message and with which emoji.

When NOT to Use:

  • To add or remove a reaction — use clickup_add_chat_reaction / clickup_delete_chat_reaction.

Returns: Each reaction's emoji name and the user who added it, plus a next_cursor when more exist.

Pagination: Cursor-based (see clickup_get_chat_messages).

Examples:

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

Error Handling: 404 → unknown message id. 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 declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral details: cursor-based pagination, return of next_cursor, and error handling for 404. No contradictions with annotations.

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 (When to Use, When NOT to Use, Returns, Pagination, Examples, Error Handling). Every sentence adds value, no fluff, and it is concise.

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 no output schema, the description covers return values (reaction emoji name, user, next_cursor), pagination, examples, and error handling. It references another tool for pagination details, which is sufficient for a read-only list tool.

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?

The input schema already describes each parameter well (e.g., limit range, cursor usage). The description adds minimal extra: it mentions cursor pagination and gives an example, but does not significantly augment the schema's parameter descriptions. Baseline 3 is appropriate.

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 emoji reactions on a chat message, with a specific verb 'List' and resource. It distinguishes from sibling tools like clickup_add_chat_reaction and clickup_delete_chat_reaction by explicitly stating when not to use.

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 explicit 'When to Use' and 'When NOT to Use' sections, referencing sibling tools for adding/removing reactions. This provides clear guidance on when to select this tool over 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