Skip to main content
Glama

clickup_folder_update

Rename a ClickUp folder by providing its ID and a new name. Only the display name is updated; returns the folder object.

Instructions

Rename a ClickUp folder. Only the folder's display name can be changed via this endpoint — to move the folder to a different space, delete and recreate. Returns the updated folder object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesID of the folder to rename. Obtain from clickup_folder_list (field: id) or clickup_folder_get.
nameYesNew display name for the folder. Must be non-empty and unique within its parent space.
Behavior3/5

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

No annotations provided, so description carries burden. It discloses that only rename is possible and returns the updated folder object, but does not mention authorization needs, rate limits, 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?

Two concise sentences, front-loaded with purpose and followed by important limitation and output information. No wasted words.

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 rename tool, the description adequately covers purpose, limitation, and return value. Lacks error scenarios but is sufficient given the tool's simplicity and no output schema requirement.

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%, and description does not add parameter-level details beyond what the schema already provides. It repeats the overall action but no extra meaning.

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?

Clearly states the verb 'rename' and the resource 'ClickUp folder', and distinguishes this from moving a folder by specifying that only the display name can be changed. Differentiates from sibling tools like clickup_folder_create and clickup_folder_delete.

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?

Explicitly states when to use (rename) and when not to (to move to a different space, delete and recreate). Provides an alternative approach via sibling tools.

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/nicholasbester/clickup-cli'

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