Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_folder

Create a new empty folder within a ClickUp Space to organize related lists. Provide the Space ID and folder name.

Instructions

Create a Folder inside a Space.

Calls POST /space/{space_id}/folder. Folders group Lists within a Space; a Folder created here starts empty (use the Lists tools to add Lists to it once t3-lists lands). ClickUp's Create Folder endpoint only accepts name in the body — to enable Folder-level statuses, call clickup_update_folder with override_statuses=true after creating.

When to Use:

  • To organize related Lists under one container inside a Space.

When NOT to Use:

  • To create a List that doesn't need a Folder (use the folderless-list tool in tools/lists.py once available).

  • To duplicate an existing structure — use clickup_create_folder_from_template.

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

Examples: params = {"space_id": "90130912", "name": "Q3 Launches"}

Error Handling: 404 means space_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
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive nature; description adds context that the folder starts empty, only accepts name initially, and returns a confirmation string or error, without contradicting annotations.

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

Conciseness4/5

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

The description is well-structured with sections, front-loaded purpose, and includes example and error handling. While slightly long, it remains useful and focused.

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?

Covers purpose, usage, behavioral details, parameters, return value, error handling, and related tools, making it fully contextual for a simple creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description reinforces the schema parameters with context about the API endpoint and an example. Though schema coverage is marked as 0%, the description adds value beyond the schema's minimal descriptions.

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 'Create a Folder inside a Space' and differentiates from sibling tools like clickup_create_folder_from_template and folderless list tool, with explicit 'When NOT to Use' section.

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, plus a tip about enabling folder-level statuses via clickup_update_folder, providing clear guidance on when to select this tool over alternatives.

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