Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_location_chat_channel

Create a chat channel tied to a Space, Folder, or List by specifying its location ID and type.

Instructions

Create a Chat channel bound to a Space, Folder, or List.

The channel's name is derived from the location, so there is no name field — pass the location id and its type instead. The location is sent as {"id": <location_id>, "type": <space|folder|list>}.

When to Use:

  • To give a specific Space/Folder/List its own conversation channel.

When NOT to Use:

  • For a standalone, named channel — use clickup_create_chat_channel.

  • For a DM — use clickup_create_direct_message.

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

Examples:

  • params = {"location_id": "901300", "location_type": "space"}

  • params = {"location_id": "L9", "location_type": "list", "visibility": "PRIVATE"}

Error Handling: 400 → bad location; 404 → location not found. 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 indicate write operation (readOnlyHint=false) and non-destructive nature. Description adds useful behavioral context: name derivation, error handling (400, 404), and return confirmation structure.

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?

Efficient structure with separate sections for purpose, usage guidance, returns, examples, and error handling. Every sentence contributes meaning without redundancy.

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?

Covers primary behavior, differentiation from siblings, parameter constraints, return value, and error scenarios. With an output schema present, the description provides sufficient context for correct tool selection and invocation.

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?

Schema has detailed descriptions for all parameters. Description adds value by explaining the combined location object format and the absence of a name field. Examples illustrate usage patterns.

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?

States clearly 'Create a Chat channel bound to a Space, Folder, or List.' Distinguishes from sibling tools like clickup_create_chat_channel (standalone) and clickup_create_direct_message (DM) through explicit when-not-to-use sections.

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?

Explicitly defines when to use (give a location its own conversation) and when not to (standalone channel, DM) with alternative tool names. Provides examples for clarity.

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