Skip to main content
Glama

create_task

Create a TickTick task in a specified project with a title, notes, due/start dates, priority, tags, reminders, and checklist subtasks.

Instructions

Create a TickTick task in a project. Dates accept YYYY-MM-DD or ISO 8601; priority accepts none/low/medium/high or 0/1/3/5.

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": {
      "projectId": "<projectId>",
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNoChecklist description.
tagsNoReplace the task tags with this list. Use [] or null to clear them.
itemsNoChecklist subtasks. Send the complete list when updating.
titleYes
contentNoTask notes/body.
dueDateNoDue date/time.
isAllDayNo
parentIdNoParent task ID to create a subtask.
priorityNoTickTick priority: 0/none, 1/low, 3/medium, 5/high.
timeZoneNoIANA time zone, for example Europe/London.
projectIdYesTickTick project ID from list_projects; use "inbox" for the Inbox.
remindersNoTickTick reminder triggers such as "TRIGGER:PT0S" or "TRIGGER:P0DT9H0M0S".
startDateNoStart date/time.
repeatFlagNoRFC 5545 recurrence rule, for example RRULE:FREQ=WEEKLY;INTERVAL=1.
repeatFromNoRecurrence base: 0 original date, 1 completion date, 2 next calendar occurrence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safety profile is covered and the description is consistent with it. The description adds the accepted date/priority encodings but says nothing about what is returned (no task ID), what happens on an invalid projectId, or any side effects such as reminder/recurrence validation.

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?

Two short sentences, purpose front-loaded, with the format caveat second and no filler. Every clause carries information; nothing is restated twice.

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 15-parameter creation tool with no output schema, the description covers the essentials an agent needs to invoke it (what it creates, where, and the two most error-prone value formats), while the rich schema carries the remaining fields. It is still thin on return values and error behavior, but the 87% schema coverage compensates for much of that.

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 description coverage is 87%, so the schema already documents most fields, and priority's mapping is duplicated verbatim from the schema. The one genuine addition is that dueDate/startDate accept YYYY-MM-DD or ISO 8601 at the top level, where the schema only says "Due date/time." That is a marginal lift over baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a TickTick task") plus the containment scope ("in a project"), so an agent immediately knows this is a write that produces a new task. It does not distinguish itself from update_task or explain when to create a subtask via parentId, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when to prefer create_task over update_task, or when to use parentId for a subtask instead of a top-level task. The only prose is value-format advice, which is parameter guidance rather than usage routing.

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