Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_folderless_list

Creates a new List directly inside a ClickUp Space that has no Folder structure. Use this tool when your Lists sit directly under a Space, not inside a Folder.

Instructions

Create a new List directly inside a Space, with no parent Folder.

Use this for Spaces that are not organized into Folders. Use clickup_create_list instead when the List belongs under an existing Folder.

When to Use:

  • The Space has no Folder structure and Lists sit directly under it.

When NOT to Use:

  • The Space is organized into Folders — use clickup_create_list so the new List lands in the right Folder.

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

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

Examples: params = {"space_id": "67890", "name": "General"} params = {"space_id": "67890", "name": "Intake", "status": "green"}

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

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?

Description discloses return format (confirmation or error string), error handling (404, 400), and lack of folder parent. Annotations are sparse (no readOnlyHint, destructiveHint), so description adds meaningful behavioral context, though no mention of side effects or auth.

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?

Well-structured with clear sections, front-loaded with purpose, and concise without unnecessary repetition.

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

Completeness5/5

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

Covers all key aspects: purpose, usage conditions, alternatives, return format, examples, error cases. Output schema exists but description aligns with it. Complete for a creation tool.

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?

Description provides examples for space_id, name, and optional status but does not explain other parameters (content, assignee, due_date, etc.). Input schema already has detailed parameter descriptions, so description adds marginal extra value beyond the schema.

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 list directly in a space without a parent folder, using specific verb and resource. It distinguishes from sibling tools like clickup_create_list and clickup_create_list_from_template_in_space.

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?

Explicit 'When to Use' and 'When NOT to Use' sections with named alternatives (clickup_create_list, clickup_create_list_from_template_in_space) provide clear context for tool selection.

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