Skip to main content
Glama

clickup_chat_channel_update

Rename a ClickUp chat channel or update its description. Returns the updated channel object.

Instructions

Rename a ClickUp chat channel or change its description. To change membership or visibility use the dedicated channel-members and channel-followers tools. Returns the updated channel object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesID of the channel to update. Obtain from clickup_chat_channel_list (field: id).
descriptionNoNew channel description shown in the channel header.
nameNoNew display name for the channel. Must be unique within the workspace.
team_idNoWorkspace (team) ID. Omit to use the default workspace from config.
Behavior4/5

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

No annotations provided, but description adds that it returns the updated channel object. Does not mention permissions or side effects, but adequate for a simple update 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?

Two sentences, front-loaded with purpose, followed by exclusion and return info. No verbose or redundant text.

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?

Given no output schema, description mentions return value. Clearly covers the two updatable fields (name, description) and identifies required param. Complete for its functionality.

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 coverage is 100%, and description adds useful hints like obtaining channel_id from list tool and uniqueness constraint for name, adding value beyond 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 renames a chat channel or changes its description, with specific verbs and resource. It distinguishes from sibling tools for membership/visibility changes.

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 directs to use channel-members and channel-followers tools for membership/visibility changes, providing clear when-not and alternatives.

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/nicholasbester/clickup-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server