Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

get_lists

Retrieve all task lists from a ClickUp folder to organize and manage project workflows.

Instructions

Get all lists in a folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesClickUp folder ID

Implementation Reference

  • Defines the 'get_lists' MCP tool, including its name, description, input schema (folder_id), and handler function that delegates to listService.getLists and formats the response.
    const getListsTool = defineTool((z) => ({
      name: "get_lists",
      description: "Get all lists in a folder",
      inputSchema: {
        folder_id: z.string().describe("ClickUp folder ID"),
      },
      handler: async (input) => {
        const { folder_id } = input;
        const response = await listService.getLists(folder_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Helper method in ListService that performs the ClickUp API request to retrieve lists in the specified folder.
    async getLists(folderId: string) {
      return this.request<{ lists: any[] }>(`/folder/${folderId}/list`);
    }
  • src/index.ts:89-91 (registration)
    Registers all tools from the tools array, including 'get_lists', with the MCP server by calling server.tool for each.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • src/index.ts:43-45 (registration)
    Includes the getListsTool in the central tools array used for MCP server registration.
    // List tools
    getListsTool,
    createListTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), implying it's likely safe and non-destructive, but doesn't specify permissions required, rate limits, pagination, or what 'all lists' entails (e.g., maximum count, format). It lacks details on error handling or response structure, leaving gaps for a tool with potential complexity.

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 ('Get all lists in a folder') that is front-loaded with the core purpose. It wastes no words and is appropriately sized for a simple tool, earning a high score for conciseness.

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

Completeness3/5

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

Given the tool's low complexity (1 parameter, 100% schema coverage, no output schema), the description is minimally adequate. It covers the basic purpose but lacks behavioral details (e.g., permissions, pagination) and usage guidelines, which are more critical since no annotations exist. It's complete enough for a simple read tool but could be improved with more context.

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 'folder_id' fully documented in the schema as 'ClickUp folder ID'. The description adds no additional parameter semantics beyond implying the folder context, so it meets the baseline of 3 where the schema handles the heavy lifting without extra value from the description.

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 'Get all lists in a folder' clearly states the action (Get) and resource (lists), specifying the scope (in a folder). It distinguishes from siblings like 'get_folders' (different resource) and 'get_list_assignees' (different aspect of lists), but doesn't explicitly differentiate from tools like 'create_list' or 'get_spaces' in terms of when to use each.

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 (e.g., needing a folder ID), exclusions, or comparisons to siblings like 'get_folders' (for broader scope) or 'create_list' (for write operations). Usage is implied by the action but not explicitly stated.

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