Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_chat_channel

Create a workspace chat channel by name. Returns existing channel if name matches. Specify visibility, users, or topic as needed.

Instructions

Create a Workspace-level Chat channel by name.

If a Channel with the given name already exists, ClickUp returns that existing Channel instead of creating a duplicate.

When to Use:

  • To open a general, non-location-bound channel (e.g. "#announcements").

When NOT to Use:

  • To attach a channel to a Space/Folder/List — use clickup_create_location_chat_channel.

  • To start a direct message — use clickup_create_direct_message.

Returns: A confirmation with the channel's name, id, and visibility.

Examples:

  • params = {"name": "announcements", "visibility": "PUBLIC"}

  • params = {"name": "team-x", "user_ids": ["123", "456"], "topic": "Team X"}

Error Handling: 400 → bad payload; 401 → bad token. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

The description states that if a channel with the given name already exists, the tool returns the existing channel instead of creating a duplicate, which is idempotent behavior. However, the annotation idempotentHint=false directly contradicts this, causing confusion about the tool's actual behavior.

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 (main description, usage, examples, errors) and is concise without extraneous information. Every sentence serves a purpose.

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?

The description covers usage guidelines, alternatives, return format, error handling, and defaults (e.g., workspace_id). While very thorough, the contradiction with idempotent hint creates a completeness issue, though the description itself is otherwise complete.

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 provides descriptions for all parameters, so the description does not need to repeat them. However, it adds value by giving concrete examples and clarifying the 'name' parameter's duplicate-handling behavior, which goes 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?

The description clearly states the tool creates a Workspace-level Chat channel by name, distinguishing it from location channels and direct messages. The verb 'create' and resource 'chat channel' are specific, and sibling differentiation is explicit.

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, naming alternatives like clickup_create_location_chat_channel and clickup_create_direct_message. It also explains the idempotent behavior of returning existing channels, providing excellent guidance.

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