Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_list

Create a new List inside an existing Folder to organize tasks by team or project. Requires a folder ID and list name; inherits Folder's statuses.

Instructions

Create a new List inside a Folder.

Lists inside a Folder normally inherit the Folder's statuses unless the Folder itself overrides Space statuses. Use clickup_create_folderless_list instead when the target Space is not organized into Folders.

When to Use:

  • Setting up a new List for a team/project that already has a Folder.

  • Programmatically scaffolding a Workspace structure Folder-by-Folder.

When NOT to Use:

  • The target Space has no Folders — use clickup_create_folderless_list.

  • Copying an established List's tasks/views/custom fields — use clickup_create_list_from_template_in_folder instead.

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

Examples: params = {"folder_id": "12345", "name": "Sprint 24", "priority": 2} params = {"folder_id": "12345", "name": "Backlog", "markdown_content": "Unscheduled work"}

Error Handling: 404 means folder_id does not exist or is not accessible; 400 usually means name is missing or a duplicate is not allowed under this Folder.

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?

The description explains inheritance of Folder statuses, clarifies that the 'status' parameter is a color not a task status, details error handling, and specifies the return format. It does not contradict annotations, which are minimal.

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 for purpose, inheritance, when/not, return, examples, and errors. It is informative without being overly verbose, though some sentences could be tightened.

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?

The description covers purpose, usage guidelines, parameter semantics, return type, and error codes. It lacks explicit mention of permissions or rate limits, but these are not critical for this simple creation tool and are implied.

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?

Given 0% schema description coverage, the description compensates by providing examples and clarifying parameter behavior (e.g., status as color, content vs. markdown_content), adding value beyond the schema's own 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 tool creates a new List inside a Folder, and distinguishes it from sibling tools like clickup_create_folderless_list and clickup_create_list_from_template_in_folder.

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?

The description includes explicit 'When to Use' and 'When NOT to Use' sections, referencing concrete scenarios and alternative tools, providing excellent guidance for an AI agent.

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