Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by mikepsinn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_list

Create a new list in a ClickUp space. Supports name-based space lookup so you don't need the space ID.

Instructions

Create a new list 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceIdNoID of the space to create the list in (optional if using spaceName instead)
spaceNameNoName of the space to create the list in - will automatically find the space by name (optional if using spaceId instead)
nameYesName of the list
contentNoDescription or content of the list
dueDateNoDue date for the list (ISO string)
priorityNoPriority of the list (1-4)
assigneeNoUser ID to assign the list to
statusNoStatus of the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the lack of API space creation but does not disclose crucial aspects like authentication requirements, whether the operation is idempotent, or what happens on failure (e.g., duplicate list name). The return value is also not described.

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 extremely concise at two sentences, with the core purpose stated first. Every word adds value, and the secondary sentence provides critical context about name-based lookup and API limitations.

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?

With 8 parameters and no output schema, the description should cover more than just space handling. It omits explanations for other parameters like content, dueDate, priority, assignee, and status, and does not describe the return value (e.g., the created list's ID or details). This leaves significant gaps for agent decision-making.

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?

While the input schema already describes all parameters (100% coverage), the description adds value by explaining the relationship between spaceId and spaceName, and the limitation that space creation is not supported. This context aids the agent in parameter selection.

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 list') and the resource ('in a ClickUp space'). It distinguishes from sibling tools like create_folder and create_list_in_folder by specifying it creates a list directly in a space, not in a folder.

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?

The description provides useful guidance on using spaceName for name-based lookup, eliminating the need for spaceId. It also explains the limitation that space creation is not supported via API. However, it does not explicitly guide when to use this tool versus create_list_in_folder for nested lists under folders.

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