Skip to main content
Glama

create_folder

Create a new folder in a ClickUp space by providing the space ID and folder name.

Instructions

Create a new folder in a ClickUp space with the specified name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe ID of the space to create the folder in
nameYesThe name of the folder

Implementation Reference

  • The MCP tool handler for 'create_folder'. Registers the tool with server.tool(), defines schema (space_id, name), calls foldersClient.createFolder(), and handles errors.
    server.tool(
      'create_folder',
      'Create a new folder in a ClickUp space with the specified name.',
      {
        space_id: z.string().describe('The ID of the space to create the folder in'),
        name: z.string().describe('The name of the folder')
      },
      async ({ space_id, name }) => {
        try {
          const result = await foldersClient.createFolder(space_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating folder:', error);
          return {
            content: [{ type: 'text', text: `Error creating folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The FoldersClient.createFolder() method that makes the actual HTTP POST request to the ClickUp API endpoint /space/{spaceId}/folder.
    async createFolder(spaceId: string, params: { name: string }): Promise<Folder> {
      return this.client.post(`/space/${spaceId}/folder`, params);
    }
  • Zod input schema for create_folder tool: requires space_id (string) and name (string).
    {
      space_id: z.string().describe('The ID of the space to create the folder in'),
      name: z.string().describe('The name of the folder')
    },
  • The tool is registered via server.tool() in setupTaskTools(), which is called from src/index.ts line 42.
    server.tool(
      'create_folder',
      'Create a new folder in a ClickUp space with the specified name.',
      {
        space_id: z.string().describe('The ID of the space to create the folder in'),
        name: z.string().describe('The name of the folder')
      },
      async ({ space_id, name }) => {
        try {
          const result = await foldersClient.createFolder(space_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating folder:', error);
          return {
            content: [{ type: 'text', text: `Error creating folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The ClickUpClient.post() method used by createFolder to make the HTTP POST request.
    async post<T = any>(endpoint: string, data?: any): Promise<T> {
      const response = await this.axiosInstance.post(endpoint, data);
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states 'Create', implying mutation, but lacks details on permissions, side effects, or error conditions.

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?

A single clear sentence with 12 words, direct and to the point. No unnecessary information.

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

Completeness4/5

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

For a simple tool with 2 params and no output schema, the description is adequate. It could mention what is returned, but the simplicity compensates.

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 description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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 action (create), resource (folder), location (in a ClickUp space), and requirement (specified name). It effectively distinguishes from sibling tools like create_list or create_task.

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

Usage Guidelines3/5

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

No guidance on when to use this tool versus alternatives like create_folderless_list. The description implies usage but provides no exclusions or context.

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

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