Skip to main content
Glama

delete_folder

Delete a folder and all its contents from ClickUp by providing the folder ID.

Instructions

Delete a folder from ClickUp. Removes the folder and its contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesThe ID of the folder to delete

Implementation Reference

  • The MCP tool handler for 'delete_folder'. Registers a tool that accepts a folder_id (string), calls foldersClient.deleteFolder(folder_id), and returns the result as JSON.
    server.tool(
      'delete_folder',
      'Delete a folder from ClickUp. Removes the folder and its contents.',
      {
        folder_id: z.string().describe('The ID of the folder to delete')
      },
      async ({ folder_id }) => {
        try {
          const result = await foldersClient.deleteFolder(folder_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting folder:', error);
          return {
            content: [{ type: 'text', text: `Error deleting folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Input schema for the delete_folder tool: expects a single required string parameter folder_id, validated with Zod.
    {
      folder_id: z.string().describe('The ID of the folder to delete')
  • Tool registration via server.tool('delete_folder', ...) inside the setupTaskTools function.
    server.tool(
      'delete_folder',
      'Delete a folder from ClickUp. Removes the folder and its contents.',
      {
        folder_id: z.string().describe('The ID of the folder to delete')
      },
      async ({ folder_id }) => {
        try {
          const result = await foldersClient.deleteFolder(folder_id);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error deleting folder:', error);
          return {
            content: [{ type: 'text', text: `Error deleting folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The FoldersClient.deleteFolder method that performs the HTTP DELETE request to /folder/{folderId} via the ClickUpClient.
    /**
     * Delete a folder
     * @param folderId The ID of the folder to delete
     * @returns Success message
     */
    async deleteFolder(folderId: string): Promise<{ success: boolean }> {
      return this.client.delete(`/folder/${folderId}`);
    }
Behavior2/5

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

No annotations provided. Description only states deletion and removal of contents, lacks detail on permanence, permissions, or reversibility.

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?

Two concise sentences with no fluff; front-loaded with essential info.

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?

Adequate for a simple 1-parameter tool, but missing behavioral context like permanent deletion or required permissions.

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 coverage is 100% for the single parameter. Description adds no extra meaning beyond the schema's parameter description.

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?

Clear verb+resource: 'Delete a folder from ClickUp. Removes the folder and its contents.' Distinct from siblings like delete_list or create_folder.

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?

No guidance on when to use this tool vs alternatives (e.g., delete list). No prerequisites or exclusions provided.

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