Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

create_list

Create a new task list within a ClickUp folder to organize and manage project workflows.

Instructions

Create a new list in a folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesClickUp folder ID
nameYesList name

Implementation Reference

  • The handler function for the create_list tool. It extracts folder_id and name from input, calls the listService.createList method, and returns the response as JSON-formatted text content.
    handler: async (input) => {
      const { folder_id, name } = input;
      const response = await listService.createList(folder_id, {
        name,
      });
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    },
  • Zod input schema for the create_list tool, defining required string parameters folder_id and name with descriptions.
    inputSchema: {
      folder_id: z.string().describe("ClickUp folder ID"),
      name: z.string().describe("List name"),
    },
  • src/index.ts:89-91 (registration)
    Registration of all tools including create_list via the MCP server's tool() method, using properties from each tool object (name, description, inputSchema, handler). The createListTool is included in the tools array.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • Supporting service method in ListService that sends a POST request to the ClickUp API endpoint to create a new list in the specified folder.
    async createList(
      folderId: string,
      params: {
        name: string;
      }
    ) {
      return this.request(`/folder/${folderId}/list`, {
        method: "POST",
        body: JSON.stringify(params),
      });
    }
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 'Create a new list,' implying a write operation, but doesn't cover critical aspects like required permissions, whether the operation is idempotent, error handling, or rate limits. This leaves significant gaps in understanding 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 a single, straightforward sentence that efficiently conveys the core action without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly for an AI agent.

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 tool's complexity as a write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens upon success (e.g., returns a list ID), error conditions, or how it fits into the broader ClickUp ecosystem with sibling tools, leaving the agent under-informed.

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 input schema has 100% description coverage, clearly documenting both parameters ('folder_id' and 'name'). The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints, so it meets the baseline for adequate but not enhanced parameter understanding.

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 ('Create') and resource ('new list in a folder'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'clickup_create_task' or 'clickup_create_doc', which also create resources in ClickUp, leaving room for ambiguity about when to use this specific tool.

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, such as sibling tools like 'clickup_create_task' or 'get_lists'. It lacks context about prerequisites, like whether the folder must exist or if there are limitations on list creation, offering minimal usage direction.

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