Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_task_members

Read-onlyIdempotent

List workspace members granted direct access to a task. Verify visibility before sharing sensitive details.

Instructions

List the Workspace members with direct access to a Task.

Calls GET /task/{task_id}/member. The response only includes members granted access directly on this Task — it excludes people who can see it via a User Group (group_id) or inherited access from the List, Folder, Space, or Workspace (team_id).

When to Use:

  • To check who can see a specific Task before sharing sensitive detail in a comment or attachment.

When NOT to Use:

  • To find who has direct access to the whole List, use clickup_get_list_members.

  • To find who is assigned to the Task (a different concept from who can see it), use the task-detail tools in the tasks module.

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

Examples: params = {"task_id": "9hz"} params = {"task_id": "DEV-123", "custom_task_ids": true, "team_id": "123456"}

Error Handling: 404 means the Task id doesn't exist or isn't visible to this token; 400 if custom_task_ids=True but team_id is missing.

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?

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses the exact API method (GET), the fact that only direct members are returned (excluding groups and inherited access), error handling for 404 and 400 codes, and example parameter sets. This enriches the agent's understanding of the tool's behavior.

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?

The description is well-structured: a concise summary, followed by API details, usage guidance, return information, example usage, and error handling. Each section is brief and pertinent, with no superfluous content.

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 simplicity (one required parameter, existing output schema, and rich annotations), the description covers all essential aspects: purpose, scope, usage guidelines, behavioral details, parameter examples, and error handling. It is complete for an agent to correctly select and invoke the tool.

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?

Although the schema has detailed descriptions for each parameter, the tool description adds value through explicit examples and error conditions related to parameters (e.g., custom_task_ids requires team_id). However, it does not mention the response_format parameter, and the description's schema coverage is low (0%), so the description does not 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?

The description explicitly states the action 'List', the resource 'Workspace members with direct access to a Task', and the scope 'direct access only'. It distinguishes from sibling tools like clickup_get_list_members and clickup_get_task, clarifying what this tool does and does not do.

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?

The description includes a 'When to Use' section for checking task visibility before sharing sensitive details, and a 'When NOT to Use' section with specific alternative tools (clickup_get_list_members for list-level access, task-detail tools for assignments). This provides clear decision-making guidance for the AI.

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