Weft

Bulk Create Tasks (Import)

bulk_create_tasks

Use this when the user wants to import many tasks at once — a CSV/JSON export from Linear, Jira, Notion or Trello, or any list of 3+ tasks from the conversation. Creates the whole batch in ONE call and one database transaction (all-or-nothing) instead of N create_task calls, so it is far cheaper on the monthly AI-call quota. Address columns by semantic ('backlog'/'todo'/'doing'/'done') or name; if the export references cycles/iterations, create the sprints first (create_sprint) and pass their sprintId per task. Tasks land in each column in array order, after the column's existing tasks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasks": "<tasks>"
    },
    "name": "bulk_create_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`tasks`	Yes	Tasks to create, in order

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

changedInput schema / properties / tasks / items / properties / assignee / description

Previous value: -"Executor: a member's name or email (case-insensitive), 'me' to assign to yourself (the calling agent), or 'none' to unassign"New value: +"Executor: a member's name, first name or email (case-insensitive), 'me' to assign to yourself (the calling agent), or 'none' to unassign"

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / tasks / items / properties / dueAt / description

Added value: +"The day this is due, as an ISO date-time (only the date part is used, e.g. \"2026-10-31T00:00:00Z\"). Put a date on anything the user said has a deadline or a day to check back — dated tasks show on the user's Weft calendar and in their subscribed Google/Apple/Outlook calendar. Pass null to clear."

addedInput schema / properties / tasks / items / properties / startAt

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The day work begins, same format as dueAt. With dueAt it makes a span on the calendar (\"measure 5–12 November\"); never after dueAt. Pass null to clear."
+}

Changed1 schema field changedOct 9, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed1 schema field changedOct 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false / destructiveHint=false, so they say little about a bulk write. The description adds the traits that actually matter: atomic all-or-nothing transaction, quota cost versus per-task calls, per-column append ordering in array order, and the cross-tool dependency on create_sprint.

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?

Front-loaded with the trigger condition and the atomicity/cost rationale before the field-level advice; every sentence carries information. It runs long, and the sprint/column ordering advice could be tightened, but nothing is filler.

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 single-array batch mutation there is no output schema, and the description never says what comes back (created IDs, per-task failures) — the one real omission. Everything an agent needs to construct a valid call and sequence it against create_sprint is present.

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 baseline is 3, but the description still adds meaning: column values accept semantic targets ('backlog'/'todo'/'doing'/'done') or names, and sprintId — which has no schema description — must come from a sprint created beforehand. It does not explain batching limits (maxItems 1000) or duplicate-title behavior.

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?

"Creates the whole batch in ONE call and one database transaction" names a specific verb (bulk create), resource (tasks), and scope (batch/import). It explicitly contrasts with N create_task calls, so an agent can distinguish it from the sibling create_task without opening either schema.

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 trigger is stated concretely ("import many tasks at once — a CSV/JSON export from Linear, Jira, Notion or Trello, or any list of 3+ tasks"), the alternative is named (create_task), and a prerequisite chain is given: create sprints first via create_sprint and pass sprintId per task.

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

All Weft tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.