Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_list_from_template_in_folder

Create a new list inside a folder by instantiating a list template, inheriting statuses, views, and tasks from the template.

Instructions

Create a new List inside a Folder by instantiating a List 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 List that should start with a known set of statuses, views, or starter Tasks defined in a template.

When NOT to Use:

  • The Space has no Folders — use clickup_create_list_from_template_in_space instead.

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

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

Examples: params = {"folder_id": "12345", "template_id": "t-15363293", "name": "Sprint 24"} params = {"folder_id": "12345", "template_id": "t-15363293", "name": "Sprint 24", "return_immediately": False}

Error Handling: 400 means name is missing or already taken; 404 means the template, folder, 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?

Discloses async behavior with return_immediately parameter, background population for large templates, and error handling for 400 and 404. No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false).

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-organized with sections, examples, and error handling. Front-loaded with main purpose. Every sentence adds value; no unnecessary words.

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 aspects: creation, async behavior, prerequisites (template discovery), error handling, and output format. Output schema exists and description explains return value. Complete for a tool with this complexity.

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?

Schema descriptions exist (e.g., for template_id, return_immediately), but description adds value by explaining template_id prefix, return_immediately default behavior, and the options parameter. With 0% schema coverage (per context), description compensates well. However, could be more concise about options.

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?

Clearly states 'Create a new List inside a Folder by instantiating a List template.' with specific verb and resource. Distinguishes from siblings by mentioning alternative tools in 'When NOT to Use' section.

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?

Includes explicit 'When to Use' and 'When NOT to Use' sections with references to sibling tools like clickup_create_list_from_template_in_space and clickup_create_list. Also advises polling with clickup_get_list for large templates.

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