Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clickup_send_chat_message

Sends a message or threaded reply to a ClickUp chat channel, supporting markdown, posts, and assignees. Provide a parent_message_id to post a reply within an existing thread.

Instructions

Send a message or threaded reply to a chat channel. Provide parent_message_id for threaded replies. Supports markdown and post types.

Input Schema

NameRequiredDescriptionDefault
typeNoType of message to send.message
contentYesMessage content to send (supports markdown).
assigneeNoUser ID to assign the message to. Use clickup_resolve_assignees to convert email, username, or "me" to user ID if needed.
followersNoArray of user IDs to add as followers of the message. Use clickup_resolve_assignees to convert emails, usernames, or "me" to user IDs if needed.
post_typeNoKind of post (required if type is 'post'). Resolved to the workspace's post subtype.
channel_idYesID of the chat channel to send the message to. Ignored when parent_message_id is set — a reply's channel is derived from its parent message.
post_titleNoTitle for the post (required if type is 'post').
workspace_idNoWorkspace ID (digits only). Only needed when you have multiple workspaces.
content_formatNoFormat of the message content.text/md
group_assigneeNoGroup ID to assign the message to.
parent_message_idNoID of the parent message to reply to. When provided, the message is sent as a threaded reply instead of a top-level channel message. Use clickup_get_chat_channel_messages to find the message ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that the tool sends a message and supports threading/markdown/post types, but says nothing about required permissions, side effects, rate limits, or expected response behavior for this write operation.

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 front-loaded with the core action, followed by the key threading condition and format support. It contains no filler and every sentence contributes to understanding the tool.

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

Completeness3/5

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

The schema is rich and fully documents the 11 parameters, which offsets much of the description's brevity. However, with no annotations and no output schema, the description could do more to explain behavioral context such as permissions or return values for a chat-sending operation.

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 description coverage is 100%, so all parameters are already documented in the input schema. The description reinforces parent_message_id for threading and mentions markdown/post support, but adds little semantic detail beyond the schema itself, making the baseline 3 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 gives a specific verb and resource: send a message or threaded reply to a chat channel. It also distinguishes chat messaging from adjacent comment/task tools by naming the channel scope, and indicates support for post types.

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

Usage Guidelines3/5

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

It gives one useful conditional: provide parent_message_id for threaded replies. However, it does not explain when to use the tool instead of alternatives such as comments, nor when to choose 'message' versus 'post' beyond the schema's enum constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools