Skip to main content
Glama

create_list_from_template_in_folder

Create a new list in a folder using a saved template to automatically populate it with predefined tasks and structure.

Instructions

Create a new list in a ClickUp folder using an existing template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesThe ID of the folder to create the list in
template_idYesThe ID of the template to use
nameYesThe name of the list

Implementation Reference

  • The tool handler function registered with the MCP server under the name 'create_list_from_template_in_folder'. It accepts folder_id, template_id, and name as string parameters, and calls listsClient.createListFromTemplateInFolder to execute the API call.
    server.tool(
      'create_list_from_template_in_folder',
      'Create a new list in a ClickUp folder using an existing template.',
      {
        folder_id: z.string().describe('The ID of the folder to create the list in'),
        template_id: z.string().describe('The ID of the template to use'),
        name: z.string().describe('The name of the list')
      },
      async ({ folder_id, template_id, name }) => {
        try {
          const result = await listsClient.createListFromTemplateInFolder(folder_id, template_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating list from template in folder:', error);
          return {
            content: [{ type: 'text', text: `Error creating list from template in folder: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • The helper function in ListsClient that makes the actual HTTP POST request to the ClickUp API endpoint /folder/{folderId}/list/template/{templateId} with the params.
    async createListFromTemplateInFolder(folderId: string, templateId: string, params: CreateListParams): Promise<List> {
      return this.client.post(`/folder/${folderId}/list/template/${templateId}`, params);
    }
  • Zod schema defining the input parameters for the tool: folder_id (string), template_id (string), and name (string).
    {
      folder_id: z.string().describe('The ID of the folder to create the list in'),
      template_id: z.string().describe('The ID of the template to use'),
      name: z.string().describe('The name of the list')
    },
  • src/index.ts:40-47 (registration)
    The tool is registered via setupTaskTools(this.server) in the ClickUpServer class constructor, which passes the MCP server instance to the setupTaskTools function.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
Behavior2/5

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

With no annotations, the description carries full burden. It only states the action without disclosing side effects (e.g., tasks copied from template), authorization needs, or return behavior. This is insufficient for a creation tool.

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?

Single sentence with no wasted words. However, it is lightweight and could benefit from slight expansion without losing conciseness.

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

Completeness3/5

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

Adequate for a simple 3-param tool, but lacks information about the template's effect on the list and the return value (e.g., list ID). Minimal but not fully complete.

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?

Schema already provides 100% description coverage for all three parameters. The description adds no extra meaning beyond what is in the schema, so baseline 3 applies.

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 action (create), resource (list), container (folder), and method (using template). It distinguishes from siblings like create_list (no template) and create_list_from_template_in_space (template in space vs folder).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., create_list_from_template_in_space, create_list). No prerequisites or contextual hints are provided, leaving the agent to infer usage from the name alone.

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/nsxdavid/clickup-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server