Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_list_members

Read-onlyIdempotent

Retrieve users with direct access to a ClickUp List to verify permissions before assigning tasks or sharing sensitive content, excluding inherited access.

Instructions

List the Workspace members with direct access to a List.

Calls GET /list/{list_id}/member. The response only includes members granted access directly on this List — it excludes people who can see the List because they belong to a User Group (group_id), or because they inherited access from the parent Folder, Space, or Workspace (team_id).

When to Use:

  • To check who has explicit access to a specific List before assigning tasks or sharing sensitive content.

  • To debug "why can't user X see this List" — if they're missing here, check Folder/Space sharing or User Group membership instead.

When NOT to Use:

  • To find who has explicit access to one Task, use clickup_get_task_members.

  • To manage User Group (ClickUp API name: "Team") membership, use clickup_get_user_groups / clickup_update_user_group.

Returns: A markdown (or JSON) list of members with id, username, and email.

Examples: params = {"list_id": "901300123456"} params = {"list_id": "901300123456", "response_format": "json"}

Error Handling: 404 means the List id doesn't exist or isn't visible to this token; 401 means CLICKUP_API_TOKEN is missing or invalid.

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 cover readOnlyHint and idempotentHint. The description adds context about response scope (excludes group/inherited access) and error handling, but does not contradict annotations.

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, front-loaded purpose, and no unnecessary 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?

The description covers purpose, usage guidelines, return format, examples, and error handling, making it complete for this simple tool.

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?

Context indicates 0% schema description coverage, but the description provides examples and explains list_id implicitly. Response_format is not elaborated beyond the schema, leading to minimal added value.

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 workspace members with direct access to a list, and distinguishes from siblings like clickup_get_task_members and clickup_get_user_groups.

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 with specific alternatives provided, guiding selection effectively.

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