Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_channels

Read-onlyIdempotent

List chat channels in a ClickUp workspace. Filter by channel type, follower status, or recent activity to find specific channels.

Instructions

List the Chat channels in a Workspace, with descriptor filters.

Returns Channels, DMs, and Group DMs the authorized user can see. Narrow the result with channel_types, is_follower, include_closed, or with_message_since. Results are cursor-paginated.

When to Use:

  • To find a channel's id before reading it (clickup_get_chat_channel), posting to it, or listing its members.

  • To enumerate only DMs (channel_types=["DM","GROUP_DM"]) or only followed channels (is_follower=true).

When NOT to Use:

  • To read messages in a channel — that lives in clickup_get_chat_messages (chat_messages module).

Returns: A list of channels (name, id, type, visibility). When more results exist the response includes a next_cursor; pass it back as cursor to page forward.

Pagination: Cursor-based and asymmetric. Loop: call once, read next_cursor from the output, then call again with cursor=<next_cursor> until it is empty.

Examples:

  • params = {"channel_types": ["CHANNEL"], "limit": 100}

  • params = {"is_follower": true, "cursor": "eyJ..."}

Error Handling: 401 → bad token; 404 → unknown Workspace id. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds significant behavioral context: cursor-based asymmetric pagination with loop instructions, error handling (401/404), and that results include only channels the user can see. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections (Returns, When to Use, When NOT to Use, Pagination, Examples, Error Handling). It is front-loaded with the main purpose. However, it is slightly verbose; some details could be more compact, but overall each sentence earns its place.

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 the tool's complexity (multiple filters, pagination, error handling), the description covers all essential aspects: return format, parameters, usage guidance, pagination loop, and error codes. It provides enough context for an agent to use the tool correctly without needing external resources.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the key parameters (channel_types, is_follower, include_closed, with_message_since) and how they narrow results. It provides concrete examples (e.g., channel_types=["CHANNEL"]). This adds meaning beyond the input schema's descriptions, which are already detailed but benefit from the narrative context.

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 'List the Chat channels in a Workspace, with descriptor filters.' It distinguishes from sibling tools like clickup_get_chat_channel (single channel) and clickup_get_chat_messages (messages), making the purpose and scope unambiguous.

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. It tells when to use this tool (find channel id, enumerate DMs, filter followed channels) and when not to (reading messages, which belongs to clickup_get_chat_messages).

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