Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_chat_channel

Idempotent

Update a ClickUp Chat channel's name, description, topic, visibility, or location by sending only the fields you want to change.

Instructions

Update a Chat channel's name, description, topic, visibility, or location.

Send only the fields you want to change (at least one is required). Text is interpreted per content_formattext/md (default) or text/plain. To re-bind the channel to another Space/Folder/List, pass location_id and location_type together.

When to Use:

  • To rename a channel, update its topic/description, or toggle visibility.

When NOT to Use:

  • To delete a channel — use clickup_delete_chat_channel.

Returns: A confirmation listing the fields that were updated.

Examples:

  • params = {"channel_id": "6-901300-8", "topic": "Sprint 42"}

  • params = {"channel_id": "6-901300-8", "visibility": "PRIVATE"}

Error Handling: 400 → bad payload; 404 → channel 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 idempotentHint=true and destructiveHint=false. Description adds valuable context: partial update behavior ('send only the fields you want to change'), content_format interpretation, and location rebind requirements (both location_id and location_type needed). No contradictions.

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?

Well-structured with clear sections: functionality, when to use/not use, returns, examples, error handling. Front-loaded with purpose, no wasted sentences.

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 all important aspects: optional fields, location rebind, content format, return confirmation, error codes. Output schema exists, so return description suffices. Siblings provided for context.

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 coverage is 0%, but description adds meaning beyond schema descriptions: explains partial updates, mutual dependency of location_id and location_type, and content_format effect. However, schema already documents each parameter; description complements but doesn't fully compensate.

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?

Description clearly states it updates a chat channel's attributes (name, description, topic, visibility, location). It distinguishes from sibling clickup_delete_chat_channel, which is explicitly mentioned in 'When NOT to Use'.

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 states when to use (rename, update topic/description, toggle visibility) and when not to use (delete, referencing the sibling tool). Provides 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