Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

get_list_assignees

Retrieve all available members who can be assigned tasks from a specific ClickUp list. Use this tool to identify potential assignees when managing task distribution in your workspace.

Instructions

Get all members (potential assignees) of a list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesClickUp list ID

Implementation Reference

  • The handler function for the 'get_list_assignees' tool. It takes the input list_id, fetches members using AssigneeService, and returns the response as JSON string in MCP format.
    handler: async (input) => {
      const { list_id } = input;
      const response = await assigneeService.getListMembers(list_id);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    },
  • Input schema defining the required 'list_id' string parameter for the tool.
    inputSchema: {
      list_id: z.string().describe("ClickUp list ID"),
    },
  • src/index.ts:27-27 (registration)
    Imports the getListAssigneesTool for registration.
    import { getListAssigneesTool } from "./controllers/assignee.controller";
  • src/index.ts:53-53 (registration)
    Adds the tool to the array of tools that are registered to the MCP server.
    getListAssigneesTool,
  • Helper method in AssigneeService that makes the API request to ClickUp to retrieve list members, used by the tool handler.
    async getListMembers(listId: string) {
      // Using the endpoint from https://developer.clickup.com/reference/getlistmembers
      return this.request<{ members: ClickUpUser[] }>(`/list/${listId}/member`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns paginated results, or details the output format. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list of members, their roles), behavioral aspects like error handling, or integration with sibling tools. For a tool with no structured support, more context is needed.

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?

The schema description coverage is 100%, with the single parameter 'list_id' fully documented in the schema as 'ClickUp list ID'. The description adds no additional meaning beyond what the schema provides, such as explaining what a 'list' is in context or how to obtain the ID. Baseline 3 is appropriate when the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get all members') and the target resource ('potential assignees of a list'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_lists' or 'get_folders', which deal with different ClickUp resources, so it doesn't fully distinguish from all siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for use, or exclusions, leaving the agent to infer usage based on the tool name and description alone.

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/Leanware-io/clickup-mcp-server'

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