Skip to main content
Glama

update_folder

Update the name of any ClickUp folder by providing its ID and new name.

Instructions

Update an existing ClickUp folder's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesThe ID of the folder to update
nameYesThe new name of the folder

Implementation Reference

  • MCP tool handler for 'update_folder'. Registers the tool with Zod schema for folder_id and name, calls foldersClient.updateFolder(), and returns the result as JSON text or an error.
    server.tool(
      'update_folder',
      'Update an existing ClickUp folder\'s name.',
      {
        folder_id: z.string().describe('The ID of the folder to update'),
        name: z.string().describe('The new name of the folder')
      },
      async ({ folder_id, name }) => {
        try {
          const result = await foldersClient.updateFolder(folder_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating folder:', error);
          return {
            content: [{ type: 'text', text: `Error updating folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Zod schema for update_folder tool: requires folder_id (string) and name (string) as input parameters.
      folder_id: z.string().describe('The ID of the folder to update'),
      name: z.string().describe('The new name of the folder')
    },
  • Registers the 'update_folder' tool on the MCP server via server.tool() in the setupTaskTools function.
    server.tool(
      'update_folder',
      'Update an existing ClickUp folder\'s name.',
      {
        folder_id: z.string().describe('The ID of the folder to update'),
        name: z.string().describe('The new name of the folder')
      },
      async ({ folder_id, name }) => {
        try {
          const result = await foldersClient.updateFolder(folder_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating folder:', error);
          return {
            content: [{ type: 'text', text: `Error updating folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • FoldersClient.updateFolder() helper method. Sends a PUT request to /folder/{folderId} with the name parameter to update a ClickUp folder.
    async updateFolder(folderId: string, params: { name: string }): Promise<Folder> {
      return this.client.put(`/folder/${folderId}`, params);
    }
Behavior2/5

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

With no annotations provided, the description must carry full behavioral transparency. It only states 'update' without detailing side effects, permission requirements, or whether it's destructive. The brief description does not suffice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence and front-loaded, which is concise. However, it is too minimal, sacrificing completeness for brevity.

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 has two required parameters, no output schema, and low complexity, the description fails to provide enough context about return values, error behavior, or how it differs from sibling tools.

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, so baseline is 3. The description adds no extra value beyond what the schema already states for the parameters (folder_id and name).

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 'update', the resource 'existing ClickUp folder', and the specific attribute 'name'. This distinguishes it from sibling tools like update_list or update_task.

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 versus alternatives like update_list or update_task. Lacks context for prerequisites or when not to use it.

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