Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_space

Create a new top-level Space in a ClickUp Workspace. Configure ClickApps like due dates and time tracking upfront. Use to set up a new team or project area.

Instructions

Create a new Space inside a Workspace.

A Space is the top-level container below a Workspace (Team) — Folders and Lists live inside it. Use features to toggle ClickApps (due dates, time tracking, tags, …). Note: custom status workflows CANNOT be set through the public API (a statuses payload is silently ignored — verified live); the new Space gets ClickUp's default statuses, editable only in the UI.

When to Use:

  • Setting up a new top-level area of work (e.g. a new team or project line).

  • Provisioning a Space with a specific ClickApp configuration up front.

When NOT to Use:

  • To create a Folder or List inside an existing Space (use the folders/lists tools).

  • To change features on a Space that already exists (use clickup_update_space).

  • To define custom statuses — the public API cannot; do it in the ClickUp UI.

Returns: A one-line confirmation naming the new Space and its id, or an Error ... string describing the failure.

Examples: params = { "name": "Engineering", "multiple_assignees": True, "features": {"due_dates": {"enabled": True}, "time_tracking": {"enabled": False}}, }

Error Handling: 400 means a malformed features payload; 401/403 mean the token lacks access to the Workspace.

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 readOnlyHint=false (write) and destructiveHint=false. Description adds that custom statuses are silently ignored and error codes for auth/validation, which is valuable beyond 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?

Well-structured with sections and front-loaded. Could be slightly more concise, but every section adds value.

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?

Covers purpose, usage, limitations (statuses), returns, and errors. Adequate for a creation tool with rich annotations and output schema.

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 description coverage is 0% (context signal), so description must compensate. It mentions 'features' and gives an example, but does not systematically describe each parameter. The schema itself has detailed descriptions, but the tool description adds marginal value.

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 'Create a new Space inside a Workspace' with specific verb and resource. Distinguishes from siblings by explicitly naming when to use folder/list tools and update_space instead.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, with specific alternatives mentioned (folders/lists tools, update_space, ClickUp UI).

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