Skip to main content
Glama
helbertparanhos

clickup-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_bulk_tasks

Create up to 100 tasks in a single list in one API call. Each task returns a success or error report, ensuring partial failures don't lose the batch.

Instructions

Create many tasks in a single List in one call (up to 100). Runs with bounded concurrency and returns a per-task success/error report, so a partial failure never loses the rest of the batch. Use to import or scaffold many tasks at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesID of the destination List for all created tasks.
tasksYesArray of task definitions to create (1–100 per call).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.0.1
    • changedInput schema / properties / list_id / description
      Previous value: -"Destination List ID."New value: +"ID of the destination List for all created tasks."
    • changedInput schema / properties / tasks / description
      Previous value: -"Array of task definitions (max 100 per call)."New value: +"Array of task definitions to create (1–100 per call)."
    • addedInput schema / properties / tasks / items / properties / assignees / description
      Added value: +"User ids to assign the task to."
    • addedInput schema / properties / tasks / items / properties / description / description
      Added value: +"Task description / body text."
    • addedInput schema / properties / tasks / items / properties / due_date / description
      Added value: +"Due date (natural language, ISO, or epoch ms)."
    • addedInput schema / properties / tasks / items / properties / name / description
      Added value: +"Task name."
    • addedInput schema / properties / tasks / items / properties / parent / description
      Added value: +"Parent task id, to create this task as a subtask."
    • addedInput schema / properties / tasks / items / properties / priority / description
      Added value: +"Priority: 1=urgent, 2=high, 3=normal, 4=low."
    • addedInput schema / properties / tasks / items / properties / status / description
      Added value: +"Status name (must exist in the List, e.g. 'to do', 'in progress')."
    • addedInput schema / properties / tasks / items / properties / tags / description
      Added value: +"Tag names to apply (must already exist in the Space)."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses batch size limit, bounded concurrency, and partial failure reporting. It does not mention authorization or rate limits, but these are less critical 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, each sentence provides essential information without redundancy.

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

Completeness5/5

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

Given no annotations and no output schema, the description covers the tool's purpose, batch constraints, concurrency, error handling, and use case. It is complete for an agent to understand when and how to invoke the 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 the description adds value by explaining batch behavior (bounded concurrency, per-task report) beyond what's in the schema. It reiterates the 'single List' constraint from the list_id parameter.

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 (many tasks in a single List), and scope (up to 100 tasks per call). It distinguishes from siblings like 'create_task' by emphasizing bulk creation and partial failure handling.

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 explicitly says 'Use to import or scaffold many tasks at once,' implying when to use. It could explicitly mention alternatives like using 'create_task' for single tasks, but the context and sibling tools make the usage clear.

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