Skip to main content
Glama
windalfin

ClickUp MCP Server

by windalfin

create_list

Create a new list directly in a ClickUp space by providing a name and either space ID or space name, enabling workspace organization without folder structure.

Instructions

Create a new list directly in a ClickUp space (not in a folder). You MUST provide either spaceId or spaceName. For creating lists inside folders, use create_list_in_folder instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the list
spaceIdNoID of the space to create the list in. Use this instead of spaceName if you have the ID.
spaceNameNoName of the space to create the list in. Alternative to spaceId - one of them MUST be provided.
contentNoDescription or content of the list
dueDateNoDue date for the list (Unix timestamp in milliseconds)
priorityNoPriority level: 1 (urgent), 2 (high), 3 (normal), 4 (low)
assigneeNoUser ID to assign the list to
statusNoStatus of the list

Implementation Reference

  • Executes the 'create_list' tool: validates input, resolves space ID, creates list using listService.createList, returns formatted response.
    export async function handleCreateList(parameters: any) {
      const { name, spaceId, spaceName, content, dueDate, priority, assignee, status } = parameters;
      
      // Validate required fields
      if (!name) {
        throw new Error("List name is required");
      }
      
      let targetSpaceId = spaceId;
      
      // If no spaceId but spaceName is provided, look up the space ID
      if (!targetSpaceId && spaceName) {
        const spaceIdResult = await workspaceService.findSpaceIDByName(spaceName);
        if (!spaceIdResult) {
          throw new Error(`Space "${spaceName}" not found`);
        }
        targetSpaceId = spaceIdResult;
      }
      
      if (!targetSpaceId) {
        throw new Error("Either spaceId or spaceName must be provided");
      }
    
      // Prepare list data
      const listData: CreateListData = {
        name
      };
    
      // Add optional fields if provided
      if (content) listData.content = content;
      if (dueDate) listData.due_date = parseInt(dueDate);
      if (priority) listData.priority = priority;
      if (assignee) listData.assignee = assignee;
      if (status) listData.status = status;
    
      try {
        // Create the list
        const newList = await listService.createList(targetSpaceId, listData);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(
              {
                id: newList.id,
                name: newList.name,
                content: newList.content,
                space: {
                  id: newList.space.id,
                  name: newList.space.name
                },
                message: `List "${newList.name}" created successfully`
              },
              null,
              2
            )
          }]
        };
      } catch (error: any) {
        throw new Error(`Failed to create list: ${error.message}`);
      }
    }
  • Defines the 'create_list' tool schema including input parameters validation (name required, spaceId or spaceName, optional content, dueDate, etc.).
    export const createListTool = {
      name: "create_list",
      description: "Create a new list directly in a ClickUp space (not in a folder). You MUST provide either spaceId or spaceName. For creating lists inside folders, use create_list_in_folder instead.",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Name of the list"
          },
          spaceId: {
            type: "string",
            description: "ID of the space to create the list in. Use this instead of spaceName if you have the ID."
          },
          spaceName: {
            type: "string",
            description: "Name of the space to create the list in. Alternative to spaceId - one of them MUST be provided."
          },
          content: {
            type: "string",
            description: "Description or content of the list"
          },
          dueDate: {
            type: "string",
            description: "Due date for the list (Unix timestamp in milliseconds)"
          },
          priority: {
            type: "number",
            description: "Priority level: 1 (urgent), 2 (high), 3 (normal), 4 (low)"
          },
          assignee: {
            type: "number",
            description: "User ID to assign the list to"
          },
          status: {
            type: "string",
            description: "Status of the list"
          }
        },
        required: ["name"]
      }
    };
  • src/server.ts:67-93 (registration)
    Registers 'create_list' tool (via createListTool) in the list returned for ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          workspaceHierarchyTool,
          createTaskTool,
          getTaskTool,
          getTasksTool,
          updateTaskTool,
          moveTaskTool,
          duplicateTaskTool,
          deleteTaskTool,
          createBulkTasksTool,
          updateBulkTasksTool,
          moveBulkTasksTool,
          deleteBulkTasksTool,
          createListTool,
          createListInFolderTool,
          getListTool,
          updateListTool,
          deleteListTool,
          createFolderTool,
          getFolderTool,
          updateFolderTool,
          deleteFolderTool
        ]
      };
    });
  • src/server.ts:124-127 (registration)
    Routes calls to 'create_list' tool to the handleCreateList handler function.
    case "create_list":
      return handleCreateList(params);
    case "create_list_in_folder":
      return handleCreateListInFolder(params);
  • src/server.ts:25-29 (registration)
    Imports the createListTool definition and handleCreateList handler from list.ts.
    createListTool, handleCreateList,
    createListInFolderTool, handleCreateListInFolder,
    getListTool, handleGetList,
    updateListTool, handleUpdateList,
    deleteListTool, handleDeleteList
Behavior3/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 the tool creates something new (implying a write/mutation operation) and specifies the location constraint ('directly in a space'), but does not mention permissions, side effects, error conditions, or response format. This leaves gaps for a mutation tool.

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 two sentences with zero waste: the first states the purpose and key constraint, the second provides usage guidance and alternative. It is front-loaded with essential information and appropriately sized for the tool's complexity.

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?

For a mutation tool with no annotations and no output schema, the description adequately covers the basic purpose and sibling differentiation, but lacks details on behavioral aspects like permissions, error handling, or return values. Given the 8 parameters and write operation, more context would be beneficial, though the schema coverage helps.

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?

Schema description coverage is 100%, so the schema fully documents all 8 parameters. The description adds minimal value beyond the schema by emphasizing the spaceId/spaceName requirement and the 'not in a folder' context, but does not provide additional syntax, format, or usage details for parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Create a new list') and resource ('directly in a ClickUp space'), and explicitly distinguishes it from the sibling tool 'create_list_in_folder' by specifying 'not in a folder'. This provides precise differentiation from alternatives.

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 provides explicit guidance on when to use this tool ('directly in a space') versus when to use an alternative ('For creating lists inside folders, use create_list_in_folder instead'). It also specifies a mandatory condition ('You MUST provide either spaceId or spaceName'), giving clear prerequisites.

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

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