Skip to main content
Glama

create_list_from_template_in_space

Create a new list in a ClickUp space by applying a template. Specify the space, template, and list name to quickly set up structured lists.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe ID of the space to create the list in
template_idYesThe ID of the template to use
nameYesThe name of the list

Implementation Reference

  • Registration and handler of the 'create_list_from_template_in_space' MCP tool. Registers the tool with schema (space_id, template_id, name) and handles the request by calling the ClickUp API client.
    server.tool(
      'create_list_from_template_in_space',
      'Create a new list in a ClickUp space using an existing template.',
      {
        space_id: z.string().describe('The ID of the space 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 ({ space_id, template_id, name }) => {
        try {
          const result = await listsClient.createListFromTemplateInSpace(space_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 space:', error);
          return {
            content: [{ type: 'text', text: `Error creating list from template in space: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Input schema for the tool using Zod validation: space_id, template_id, and name (all strings).
    {
      space_id: z.string().describe('The ID of the space 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')
    },
  • The actual API client method that sends a POST request to the ClickUp API endpoint /space/{spaceId}/list/template/{templateId} to create a list from a template in a space.
    async createListFromTemplateInSpace(spaceId: string, templateId: string, params: CreateListParams): Promise<List> {
      return this.client.post(`/space/${spaceId}/list/template/${templateId}`, params);
    }
  • Type definition for CreateListParams used as the parameter type for the handler method.
    export interface CreateListParams {
      name: string;
      // ...other parameters for creating a list...
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. No disclosure of side effects, permissions, or behavior like whether settings are copied from template.

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?

Extremely concise (one sentence) with no fluff. However, the brevity omits important details, preventing a perfect score.

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

Completeness2/5

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

Given simple parameters and no output schema, the description should mention return value or templates must exist. Missing such context makes it incomplete.

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 coverage is 100% with clear parameter descriptions. The description adds no additional context beyond the schema, so baseline of 3.

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 specific action: creating a list in a space using a template. It distinguishes from siblings like create_list (no template) and create_list_from_template_in_folder (folder context).

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 vs alternatives like create_list or create_list_from_template_in_folder. Prerequisites (e.g., existence of template) not mentioned.

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