Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_folder

Idempotent

Rename a ClickUp Folder and optionally toggle its custom status override to control whether it inherits statuses from the Space or uses folder-level ones.

Instructions

Rename a Folder and/or toggle its status-override setting.

Calls PUT /folder/{folder_id}. Setting override_statuses=True moves this Folder (and Lists inside it, unless a List overrides further) from inheriting the Space's status workflow to a Folder-level custom one; this endpoint only flips the flag — inspect the resulting statuses with clickup_get_folder. Note: the status definitions themselves cannot be set through the public API (same limitation as Space statuses, verified live for Spaces) — define custom statuses in the ClickUp UI.

When to Use:

  • To rename a Folder.

  • To turn Folder-level status overrides on or off.

When NOT to Use:

  • To change a single List's statuses — that is scoped to the List/Space tools, not this endpoint.

Returns: A confirmation string with the Folder's new name, or an Error ... string.

Examples: params = {"folder_id": "456", "name": "Q3 Launches (Renamed)", "override_statuses": True}

Error Handling: 404 means folder_id doesn't exist or isn't accessible; 400 means the name is missing/invalid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses that the endpoint only flips a flag, that status definitions cannot be set via API, and gives a recommendation to inspect results with another tool. This adds significant context beyond the annotations.

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 well-structured with sections for use cases, examples, and error handling. Every sentence is informative, and the content is front-loaded with the core purpose.

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

Completeness5/5

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

Given the complexity of the status-override feature, the description adequately explains the behavior, limitations, and error codes. The presence of an output schema means return values are not the description's responsibility, but it still mentions the return format.

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 already provides clear descriptions for each parameter (100% coverage as seen in the schema). The tool description adds marginal extra context about the status override behavior, but the schema already covers the basic semantics, so 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 tool renames a Folder and/or toggles its status-override setting. It names the specific HTTP endpoint and distinguishes from sibling tools by noting that List-level status changes require different tools.

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?

Explicit 'When to Use' and 'When NOT to Use' sections are present, with a concrete example and clear guidance to avoid misuse for List-level statuses.

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

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