Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_folder_from_template

Replay a Folder template to create a new Folder with its Lists, statuses, and Views, instead of building from scratch.

Instructions

Create a new Folder by replaying a Folder template.

Calls POST /space/{space_id}/folder_template/{template_id}. Fetch available template ids (always t--prefixed) with clickup_get_folder_templates first.

When to Use:

  • To stamp out a repeatable Folder structure (Lists, statuses, views) instead of rebuilding it by hand with clickup_create_folder.

When NOT to Use:

  • To create a plain empty Folder — use clickup_create_folder.

Returns: A confirmation string with the new Folder's id, or an Error ... string. If options.return_immediately is left at ClickUp's default, the template content may still be populating asynchronously — re-check with clickup_get_folder.

Examples: params = { "space_id": "90130912", "template_id": "t-7162342", "name": "Q4 Launch (from template)", "options": {"include_views": True, "old_due_date": True}, }

Error Handling: 404 means space_id or template_id doesn't exist; 400 means the name is missing/invalid.

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 when return_immediately is default, suggests re-checking with clickup_get_folder. No contradiction with annotations.

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?

Well-organized with sections, examples, and error handling. Slightly lengthy but each part adds value.

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 use cases, async behavior, error codes, return type, and provides an example. Output schema exists but description adequately explains return value.

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 does not elaborate on parameters beyond schema; schema has detailed descriptions so burden is shared, but description adds minimal param insight.

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 Folder from a template, and distinguishes it from clickup_create_folder for plain empty folders.

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 direct reference to sibling tool clickup_create_folder, and prerequisite mention of clickup_get_folder_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