Skip to main content
Glama

create_list_in_folder

Create a new list in a ClickUp folder by specifying folder or space names, avoiding the need for IDs. Add list name, content, and status.

Instructions

Create a new list in a ClickUp folder. Supports direct name-based lookup for folders and spaces - no need to know IDs. If the specified folder doesn't exist, you can create it using create_folder. If the space doesn't exist, it must be created through the ClickUp web interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdNoID of the folder to create the list in (optional if using folderName instead)
folderNameNoName of the folder to create the list in - will automatically find the folder by name (optional if using folderId instead)
spaceIdNoID of the space containing the folder (optional if using spaceName instead)
spaceNameNoName of the space containing the folder - will automatically find the space by name (optional if using spaceId instead)
nameYesName of the list
contentNoDescription or content of the list
statusNoStatus of the list
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses name-based lookup and fallback actions for missing folder/space. However, it does not explain behavior when multiple matches exist for folder or space names, nor does it specify parameter precedence when both ID and name are provided.

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?

Three sentences, each adding distinct value: purpose, key feature (name lookup), and fallback guidance. Every sentence earns its place; no redundancy.

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?

Given 7 parameters and no output schema, the description covers creation and resolution behavior. However, it lacks details on handling ambiguous names, parameter precedence, and error conditions, leaving minor gaps.

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 the baseline is 3. The description adds context like 'name-based lookup' and references to create_folder, but most parameter details are already in the schema descriptions. No significant additional semantic value.

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 list in a ClickUp folder, distinguishing it from sibling tools like create_list (likely workspace-level) and create_folder (for folders). The verb 'create' and resource 'list in a folder' are specific and unambiguous.

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?

The description provides explicit guidance: when the folder doesn't exist, use create_folder; when the space doesn't exist, create it via web interface. This helps the agent decide when to use this tool versus alternatives.

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

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