Skip to main content
Glama

create_folderless_list

Create a new list in a ClickUp space without placing it in a folder. Provide the space ID and list name.

Instructions

Create a new list directly in a ClickUp space without placing it in a folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe ID of the space to create the folderless list in
nameYesThe name of the folderless list

Implementation Reference

  • The handler function that executes the create_folderless_list tool logic. It calls listsClient.createFolderlessList with space_id and name, returning the result or an error.
    async ({ space_id, name }) => {
      try {
        const result = await listsClient.createFolderlessList(space_id, { name });
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
        };
      } catch (error: any) {
        console.error('Error creating folderless list:', error);
        return {
          content: [{ type: 'text', text: `Error creating folderless list: ${error.message}` }],
          isError: true
        };
      }
  • The tool registration with Zod schema defining the input parameters: space_id (string) and name (string).
    server.tool(
      'create_folderless_list',
      'Create a new list directly in a ClickUp space without placing it in a folder.',
      {
        space_id: z.string().describe('The ID of the space to create the folderless list in'),
        name: z.string().describe('The name of the folderless list')
      },
  • Registration of the create_folderless_list tool via server.tool(), including its schema and handler.
    server.tool(
      'create_folderless_list',
      'Create a new list directly in a ClickUp space without placing it in a folder.',
      {
        space_id: z.string().describe('The ID of the space to create the folderless list in'),
        name: z.string().describe('The name of the folderless list')
      },
      async ({ space_id, name }) => {
        try {
          const result = await listsClient.createFolderlessList(space_id, { name });
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error creating folderless list:', error);
          return {
            content: [{ type: 'text', text: `Error creating folderless list: ${error.message}` }],
            isError: true
          };
        }
      }
  • The ListsClient.createFolderlessList helper method that makes the actual API POST request to /space/{spaceId}/list.
    /**
     * Create a new folderless list in a space
     * @param spaceId The ID of the space to create the list in
     * @param params The list parameters
     * @returns The created list
     */
    async createFolderlessList(spaceId: string, params: CreateListParams): Promise<List> {
      return this.client.post(`/space/${spaceId}/list`, params);
    }
  • The CreateListParams interface used as the params type for the createFolderlessList method.
    export interface CreateListParams {
      name: string;
      // ...other parameters for creating a list...
    }
Behavior3/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the fundamental action but does not mention required permissions, idempotency, or error states. The behavioral transparency is minimal but not misleading.

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 a single, focused sentence with no extraneous information. Every word contributes meaning.

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

Completeness4/5

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

For a simple create operation with two parameters, the description is nearly complete. It could mention the expected outcome or response, but the core purpose is clearly communicated.

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%, so baseline is 3. The description adds no additional parameter context beyond what the schema provides.

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 uses a specific verb ('Create') and resource ('folderless list'), and clearly distinguishes it from sibling tools like 'create_list' by specifying 'without placing it in a folder'.

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

Usage Guidelines4/5

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

It states the context (directly in a space without a folder), which implies when to use, but does not explicitly provide when-not-to-use or alternative tools. However, the sibling context makes the distinction clear.

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