Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_list_from_template_in_space

Create a new folderless List in a ClickUp Space using a template. Instantiates a list with predefined statuses, views, and tasks directly in the space without a folder.

Instructions

Create a new folderless List inside a Space by instantiating a template.

Use clickup_get_list_templates to discover available template_id values (they carry a t- prefix, e.g. t-15363293). With return_immediately=True (the default) the response's List id may represent a List that is still being populated in the background for large templates — poll with clickup_get_list if you need to confirm completion.

When to Use:

  • Scaffolding a new folderless List that should start with a known set of statuses, views, or starter Tasks defined in a template.

When NOT to Use:

  • The target Space uses Folders — use clickup_create_list_from_template_in_folder instead.

  • No template fits — use clickup_create_folderless_list for a blank List.

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

Examples: params = {"space_id": "67890", "template_id": "t-15363293", "name": "General"}

Error Handling: 400 means name is missing or already taken; 404 means the template or space was not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate a write operation (readOnlyHint false) and not destructive. The description adds key behavioral details: with return_immediately=True, the returned List id may represent a List still being populated in the background for large templates, and recommends polling with clickup_get_list to confirm completion. Also covers error handling.

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 well-structured with clear sections: purpose, prerequisites, usage guidelines, return value, examples, and error handling. Every sentence adds value, and it is 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?

Given no output schema, the description adequately explains the return value (confirmation string with id or error). It includes prerequisites, behavioral notes on background population, and error codes. The tool's complexity is well-covered.

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?

The input schema already describes all parameters with descriptions. The tool description adds context for template_id (prefix) and return_immediately (effect), but does not detail the options parameter; however, the schema covers it. Overall, the description complements the schema well.

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 folderless List inside a Space by instantiating a template. It distinguishes from siblings by naming alternatives like clickup_create_list_from_template_in_folder and clickup_create_folderless_list, and provides specific use cases.

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 provide clear context. It specifies scaffolding a folderless List with a known template, and warns against using when the space uses folders or when no template fits, directing to alternative tools.

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