Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_add_chat_reaction

Idempotent

Add an emoji reaction to a ClickUp Chat message. Provide the message ID and lower-case emoji name (e.g., 'thumbsup').

Instructions

Add an emoji reaction to a Chat message.

reaction is the lower-case emoji name (e.g. thumbsup, heart, tada); it is lower-cased for you.

When to Use:

  • To react to a message with an emoji.

When NOT to Use:

  • To remove a reaction — use clickup_delete_chat_reaction.

  • To list reactions — use clickup_get_chat_message_reactions.

Returns: A confirmation naming the emoji and message.

Examples:

  • params = {"message_id": "abc123", "reaction": "thumbsup"}

Error Handling: 400 → unknown emoji name; 404 → unknown message. 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 provide readOnlyHint=false, destructiveHint=false, idempotentHint=true. Description adds that reactions are lower-cased automatically and provides error codes, adding context 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.

Conciseness5/5

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

Well-structured with clear sections, an example, and error handling. Every sentence adds value without being verbose.

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 tool's simplicity, annotations, and presence of an output schema, the description covers purpose, usage, parameters, and errors adequately.

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 has descriptions for each parameter. The description adds useful context like lower-casing behavior and default workspace, but schema coverage is high.

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 'Add an emoji reaction to a Chat message.' It uses a specific verb-resource pair and distinguishes from sibling tools like clickup_delete_chat_reaction and clickup_get_chat_message_reactions.

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?

Explicit 'When to Use' and 'When NOT to Use' sections with specific alternative tool names. Error handling details further guide usage.

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