Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_send_chat_message

Send a chat message to a ClickUp channel. Create plain messages or rich posts using subtypes for announcements, discussions, and more.

Instructions

Post a new message to a Chat channel.

Defaults to a plain 'message'. For a rich 'post' (Announcement/Discussion/Idea/ Update), set message_type='post' and pass the subtype id in post_data={"subtype": {"id": "..."}} — get the id from clickup_get_chat_subtypes.

When to Use:

  • To send a message into a channel.

When NOT to Use:

  • To reply within a thread — use clickup_send_chat_reply.

  • To change an existing message — use clickup_update_chat_message.

Returns: A confirmation with the new message's id and channel.

Examples:

  • params = {"channel_id": "6-901...", "content": "Deploy is green ✅"}

  • params = {"channel_id": "6-901...", "content": "Q3 kickoff", "message_type": "post", "post_data": {"subtype": {"id": "123"}}}

Error Handling: 400 → bad body (e.g. content too long); 404 → unknown channel. 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 present (readOnlyHint=false, etc.), but description adds meaningful context: return format (confirmation with id and channel), error codes (400, 404), and details on post_data usage. No contradiction.

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?

Concise and well-structured: main purpose, defaults, when-to-use/not, returns, examples, error handling. Every sentence adds value, no 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?

Covers usage, parameters, return values, errors, and references sibling tool for subtypes. Lacks mention of rate limits or authentication, but annotations (openWorldHint=true) and output schema compensate. Very complete for a chat message tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description thoroughly explains parameters: default message_type, post_data usage with reference to clickup_get_chat_subtypes, assignee, followers, content_format, etc. It adds significant value beyond 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 states 'Post a new message to a Chat channel' and distinguishes plain messages from rich posts (Announcement/Discussion/Idea/Update). Explicitly differentiates from sibling tools clickup_send_chat_reply and clickup_update_chat_message.

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?

Has explicit 'When to Use' and 'When NOT to Use' sections, naming specific alternative tools for replying in a thread and updating messages. Includes examples and error handling.

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