Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_chat_channel_members

Read-onlyIdempotent

Retrieve the list of users who are members of a specific ClickUp Chat channel. Use this to audit channel access and manage permissions.

Instructions

List the users who are members of a Chat channel.

Members can access and post to the channel. Results are cursor-paginated.

When to Use:

  • To audit who has access to a private channel or DM.

When NOT to Use:

  • To see subscribers only — use clickup_get_chat_channel_followers.

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

Pagination: Cursor-based. Loop with cursor=<next_cursor> until it is empty.

Examples:

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

  • params = {"channel_id": "6-901300-8", "cursor": "eyJ...", "limit": 100}

Error Handling: 404 → channel not found. 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 readOnly, idempotent, non-destructive. The description adds rich behavioral context: cursor-based pagination, error handling (404), and response structure (list of users with next_cursor), beyond what annotations provide.

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-organized into sections: purpose, usage guidelines, return format, pagination, examples, error handling. Every sentence is informative 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 all necessary aspects: purpose, when/not to use, parameter examples, pagination mechanism, error handling, and return format. With annotations and output schema present, the description is fully 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 has detailed descriptions for all parameters (limit, cursor, channel_id, workspace_id, response_format). The description supplements with usage examples and pagination notes, adding value 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 lists members of a chat channel with a specific verb ('list') and resource. It distinguishes from a sibling tool by explicitly noting when to use an alternative for subscribers.

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?

Provides explicit when-to-use ('audit who has access') and when-not-to-use with a named alternative ('use clickup_get_chat_channel_followers for subscribers'), offering clear 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