Skip to main content
Glama
windalfin

ClickUp MCP Server

by windalfin

update_folder

Modify existing ClickUp folder properties like name or status settings to organize workspace tasks effectively.

Instructions

Modify an existing folder's properties. Valid parameter combinations:

  1. Use folderId alone (preferred)

  2. Use folderName + (spaceId or spaceName)

At least one update field (name or override_statuses) must be provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdNoID of folder to update (preferred). Use this instead of folderName if you have it.
folderNameNoName of folder to update. When using this, you MUST also provide spaceId or spaceName.
spaceIdNoID of space containing the folder (required with folderName). Use this instead of spaceName if you have it.
spaceNameNoName of space containing the folder (required with folderName). Only use if you don't have spaceId.
nameNoNew name for the folder
override_statusesNoWhether to override space statuses with folder-specific statuses

Implementation Reference

  • The handler function that implements the core logic for the 'update_folder' tool. It resolves the target folder ID (using lookups if name-based), validates inputs, constructs update data, invokes the folder service, and returns a formatted response.
    export async function handleUpdateFolder(parameters: any) {
      const { folderId, folderName, name, override_statuses, spaceId, spaceName } = parameters;
      
      let targetFolderId = folderId;
      
      // If no folderId provided but folderName is, look up the folder ID
      if (!targetFolderId && folderName) {
        let targetSpaceId = spaceId;
        
        // If no spaceId provided but spaceName is, look up the space ID first
        if (!targetSpaceId && spaceName) {
          const spaceIdResult = await workspaceService.findSpaceByName(spaceName);
          if (!spaceIdResult) {
            throw new Error(`Space "${spaceName}" not found`);
          }
          targetSpaceId = spaceIdResult.id;
        }
        
        if (!targetSpaceId) {
          throw new Error("Either spaceId or spaceName must be provided when using folderName");
        }
        
        const folderResult = await folderService.findFolderByName(targetSpaceId, folderName);
        if (!folderResult) {
          throw new Error(`Folder "${folderName}" not found in space`);
        }
        targetFolderId = folderResult.id;
      }
      
      if (!targetFolderId) {
        throw new Error("Either folderId or folderName must be provided");
      }
      
      // Ensure at least one update field is provided
      if (!name && override_statuses === undefined) {
        throw new Error("At least one of name or override_statuses must be provided for update");
      }
    
      // Prepare update data
      const updateData: Partial<CreateFolderData> = {};
      if (name) updateData.name = name;
      if (override_statuses !== undefined) updateData.override_statuses = override_statuses;
    
      try {
        // Update the folder
        const updatedFolder = await folderService.updateFolder(targetFolderId, updateData);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(
              {
                id: updatedFolder.id,
                name: updatedFolder.name,
                space: {
                  id: updatedFolder.space.id,
                  name: updatedFolder.space.name
                },
                message: `Folder "${updatedFolder.name}" updated successfully`
              },
              null,
              2
            )
          }]
        };
      } catch (error: any) {
        throw new Error(`Failed to update folder: ${error.message}`);
      }
    }
  • The tool schema defining the name 'update_folder', description, and inputSchema for parameter validation.
    export const updateFolderTool = {
      name: "update_folder",
      description: "Modify an existing folder's properties. Valid parameter combinations:\n1. Use folderId alone (preferred)\n2. Use folderName + (spaceId or spaceName)\n\nAt least one update field (name or override_statuses) must be provided.",
      inputSchema: {
        type: "object",
        properties: {
          folderId: {
            type: "string",
            description: "ID of folder to update (preferred). Use this instead of folderName if you have it."
          },
          folderName: {
            type: "string",
            description: "Name of folder to update. When using this, you MUST also provide spaceId or spaceName."
          },
          spaceId: {
            type: "string",
            description: "ID of space containing the folder (required with folderName). Use this instead of spaceName if you have it."
          },
          spaceName: {
            type: "string",
            description: "Name of space containing the folder (required with folderName). Only use if you don't have spaceId."
          },
          name: {
            type: "string",
            description: "New name for the folder"
          },
          override_statuses: {
            type: "boolean",
            description: "Whether to override space statuses with folder-specific statuses"
          }
        },
        required: []
      }
    };
  • src/server.ts:138-139 (registration)
    Registers the tool dispatch: routes 'update_folder' calls to the handleUpdateFolder handler in the MCP server request handler.
    case "update_folder":
      return handleUpdateFolder(params);
  • src/server.ts:88-91 (registration)
    Includes updateFolderTool in the list of available tools returned by the listTools MCP endpoint.
      getFolderTool,
      updateFolderTool,
      deleteFolderTool
    ]
  • Helper service method invoked by the handler to perform the actual ClickUp API updateFolder call via HTTP PUT.
    async updateFolder(folderId: string, updateData: Partial<CreateFolderData>): Promise<ClickUpFolder> {
      try {
        this.logOperation('updateFolder', { folderId, ...updateData });
        
        const response = await this.client.put<ClickUpFolder>(
          `/folder/${folderId}`,
          updateData
        );
        
        return response.data;
      } catch (error) {
        throw this.handleError(error, `Failed to update folder ${folderId}`);
      }
    }
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. While 'Modify' implies a mutation operation, the description doesn't address critical behavioral aspects: what permissions are required, whether changes are reversible, what happens to existing properties not mentioned, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, 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 efficiently structured with three sentences: a clear purpose statement, specific parameter combination rules, and a requirement for update fields. Every sentence earns its place by providing essential information without redundancy. The front-loaded purpose statement makes the tool's function immediately clear.

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?

For a mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. While it covers parameter combinations and update requirements, it lacks critical information about permissions, side effects, error handling, and response format. The absence of behavioral transparency and output information makes this inadequate for confident tool invocation despite the good parameter documentation.

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%, so all parameters are already documented in the schema. The description adds minimal value beyond the schema by emphasizing the preferred parameter combination (folderId alone) and stating that at least one update field must be provided. However, it doesn't provide additional semantic context about what 'override_statuses' means in practice or how name changes affect folder hierarchy.

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 verb ('Modify') and resource ('existing folder's properties'), making the purpose immediately understandable. It distinguishes this from creation tools like 'create_folder' and deletion tools like 'delete_folder' by focusing on modification. However, it doesn't explicitly differentiate from other update tools like 'update_list' or 'update_task' in terms of what makes folder updates unique.

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

Usage Guidelines4/5

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

The description provides explicit guidance on parameter combinations: folderId alone (preferred) or folderName with spaceId/spaceName. It also states that at least one update field (name or override_statuses) must be provided. This gives clear usage rules, though it doesn't explicitly mention when to use this tool versus alternatives like 'update_list' or 'update_task' for different resource types.

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