ClickUp MCP Server

create_folder

Create a folder in a ClickUp space using space name or ID, with optional status override.

Instructions

Create a new folder in a ClickUp space. Supports direct name-based lookup for spaces - no need to know the space ID. If the specified space doesn't exist, you can create it through the ClickUp web interface (space creation via API not supported).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

Name	Required	Description
`spaceId`	No	ID of the space to create the folder in (optional if using spaceName instead)
`spaceName`	No	Name of the space to create the folder in - will automatically find the space by name (optional if using spaceId instead)
`name`	Yes	Name of the folder
`override_statuses`	No	Whether to override space statuses

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1May 26, 2026

TDQS

A3.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It mentions the name lookup and API limitation but omits behavioral details such as required permissions, error handling, or whether the operation is idempotent.

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 sentences, no wasted words, and the main purpose is front-loaded. Achieves maximum conciseness.

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

Completeness3/5

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

Lacks details about return values, error handling, or required permissions. For a simple creation tool without output schema or annotations, this is borderline adequate but not fully complete.

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 input schema already describes all parameters (100% coverage). The description adds value by explaining the name-lookup feature and the fallback for missing spaces, supplementing the schema for spaceId/spaceName.

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 new folder in a ClickUp space') and highlights the space name-based lookup, distinguishing it from sibling tools that handle tasks or lists.

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?

Provides practical guidance on when to use name-based lookup and explains that space creation is not supported via API, but does not explicitly differentiate from other creation tools like create_list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server