Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_direct_message

Create a direct-message Chat channel with up to 15 users, supporting 1:1, group, or self DMs. Returns existing channel if same participant set already exists.

Instructions

Create (or return) a direct-message Chat channel with up to 15 users.

One recipient id makes a 1:1 DM; two or more make a Group DM. Omit user_ids (or pass an empty list) to create a Self DM. ClickUp returns the existing DM channel if one already exists for the same participant set.

When to Use:

  • To message one or a few users directly rather than in a shared channel.

When NOT to Use:

  • For a named or location-bound channel — use clickup_create_chat_channel or clickup_create_location_chat_channel.

Returns: A confirmation with the DM channel's id and participant count.

Examples:

  • params = {"user_ids": ["123"]}

  • params = {"user_ids": ["123", "456", "789"]}

  • params = {} # Self DM

Error Handling: 400 → more than 15 users / bad id; 401 → bad token. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds context about the tool being idempotent in behavior (returns existing DM if same participant set), which is at odds with the annotation 'idempotentHint: false'. This contradiction reduces reliability. Otherwise, it provides error handling details but no additional behavioral traits beyond what annotations already indicate (readOnlyHint=false, destructiveHint=false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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, Examples, Error Handling). It is front-loaded with the main purpose. Although somewhat lengthy, every sentence contributes useful information.

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?

The description covers all key aspects: different DM types, participant limits, idempotency (existing channel returned), error codes, and examples. An output schema exists, so return value explanation is unnecessary. The description is thorough for this tool's complexity.

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 description adds value for 'user_ids' by explaining 1:1, Group, and Self DM scenarios with examples. However, 'workspace_id' is not mentioned in the description; the schema already adequately describes it. Since schema description coverage is effectively high (the schema contains descriptions for both parameters), the description adds moderate value.

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 action ('Create (or return)') and resource ('direct-message Chat channel') and specifies the limit of 15 users. It distinguishes from sibling tools 'clickup_create_chat_channel' and 'clickup_create_location_chat_channel' by mentioning they are for named or location-bound channels.

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 provide clear guidance, including specific alternative tools to use instead. This helps the agent select the correct tool.

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