Skip to main content
Glama
helbertparanhos

clickup-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_folderless_list

Create a new list directly under a ClickUp Space without placing it in a folder. Specify name, description, due date, priority, default assignee, and status.

Instructions

Create a new List directly under a Space (not inside any Folder), optionally setting description, due date, priority, default assignee and status. Returns the created List with its id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID of the Space to create the List in.
nameYesName for the new List.
contentNoList description / notes shown at the top of the List.
due_dateNoDue date for the List. Accepts natural language ('tomorrow', 'in 3 days'), ISO date, or epoch milliseconds.
due_date_timeNoIf true, the due_date includes a specific time of day (not just a date).
priorityNoPriority: 1=urgent, 2=high, 3=normal, 4=low.
assigneeNoUser id set as the default assignee for new tasks in the List.
statusNoList color/status name (the List's accent label).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.1
    • changedInput schema / properties / assignee / description
      Previous value: -"Default assignee user id."New value: +"User id set as the default assignee for new tasks in the List."
    • changedInput schema / properties / content / description
      Previous value: -"List description."New value: +"List description / notes shown at the top of the List."
    • changedInput schema / properties / due_date / description
      Previous value: -"Date as ISO string, epoch ms, or relative (\"tomorrow\", \"in 3 days\", \"+2h\")."New value: +"Due date for the List. Accepts natural language ('tomorrow', 'in 3 days'), ISO date, or epoch milliseconds."
    • addedInput schema / properties / due_date_time / description
      Added value: +"If true, the due_date includes a specific time of day (not just a date)."
    • addedInput schema / properties / name / description
      Added value: +"Name for the new List."
    • changedInput schema / properties / priority / description
      Previous value: -"1=urgent .. 4=low."New value: +"Priority: 1=urgent, 2=high, 3=normal, 4=low."
    • changedInput schema / properties / space_id / description
      Previous value: -"Space ID."New value: +"ID of the Space to create the List in."
    • changedInput schema / properties / status / description
      Previous value: -"List color/status name."New value: +"List color/status name (the List's accent label)."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Description states it returns the created List with its id, but lacks details on side effects, error handling, or permissions. Without annotations, the description carries the burden and could be more thorough.

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?

Single sentence with key purpose upfront, no redundant information. Efficient and well-structured.

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 8 parameters and no output schema, the description covers the core purpose and key optional settings. Could mention uniqueness constraints or behavior on error, but sufficient for a create tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 value by summarizing optional fields like description, due date, priority, default assignee, and status, providing context beyond the schema.

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?

Description clearly states the tool creates a List directly under a Space, not inside any Folder. The verb 'create' and resource 'List' are specific, and it differentiates from siblings like create_list_in_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?

Description implies usage when a List should be in a Space without a Folder. It does not explicitly state when not to use or mention alternatives, but the context is clear that this is for folderless creation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools