Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_space

Create a new space in a ClickUp team by providing the team ID and space name. Set optional features like tags, due dates, and multiple assignees.

Instructions

Create a new space in a ClickUp team/workspace.

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": {
      "team_id": "<team_id>",
      "name": "<name>"
    },
    "name": "create_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the space
team_idYesThe ID of the team (workspace)
featuresNoSpace features configuration
multiple_assigneesNoAllow multiple assignees (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action and target. It does not disclose permissions, side effects, name uniqueness constraints, or what happens if the team does not exist.

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 a single sentence with no redundancy or filler. It efficiently conveys the core purpose and location of the new space.

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

Completeness2/5

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

The tool has four parameters including a nested features object, and no output schema. The description does not explain return values, side effects, or how to interpret the response. It relies entirely on the input schema, which covers parameters but not behavioral outcomes.

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 provides complete descriptions for all four parameters (100% coverage), so the tool description does not need to repeat parameter details. It adds no extra semantic context beyond what the schema already provides.

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 uses a specific verb ('create') and resource ('space'), with the context 'in a ClickUp team/workspace.' This clearly distinguishes it from sibling tools like create_folder, create_list, or update_space.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, such as create_folder or create_list. The description does not mention preconditions, exclusions, or scenarios where a different tool should be preferred.

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

Deploy Server

Other Tools