Skip to main content
Glama

create_project

Create a new project in TickTick with custom name, color, view mode (list, kanban, timeline), and optional folder assignment. Supports task and note types.

Instructions

Create a new TickTick project (list).

[Category: Projects]  [Auth: V1 + V2 when group_id is provided]
[Related: list_projects, update_project, delete_project, list_project_folders]
[Workflow: Create project → manage_columns (for kanban) → create_task]

Args:
    name: Project name (required).
    color: Hex color, e.g. "#F18181".
    kind: "TASK" (default) or "NOTE".
    view_mode: "list", "kanban", or "timeline".
    group_id: Folder ID to file project in (from list_project_folders).

⚠️  group_id ALWAYS requires a V2 follow-up — handled automatically here:
    The V1 create endpoint silently ignores groupId in the payload (no error,
    no warning — it just doesn't persist). This tool works around it by:
    1. Creating the project via V1 to obtain the new project ID.
    2. Immediately calling V2 POST /batch/project to assign the groupId.
    The returned dict reflects groupId correctly. Verify with full_sync()
    if needed — V1 list_projects always shows groupId=null regardless.

⚠️  Never try to assign group_id via a raw V1 update — it silently fails.
    Always go through update_project(group_id=...) which also uses V2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
colorNo
kindNoTASK
view_modeNo
group_idNo
Behavior5/5

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

With no annotations provided, the description fully carries the burden of disclosing behavior. It details the V1/V2 workaround for group_id, warns about silent failures, and explains the automatic follow-up call. This is excellent transparency.

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?

The description is structured with sections (Category, Auth, Related, Workflow, Args) and a detailed warning. While the warning is lengthy, it is necessary. The structure is clear and front-loaded with the core purpose.

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 no annotations, no output schema, and 5 undocumented parameters, the description compensates well by explaining the tricky group_id behavior and parameter options. However, it lacks details on return value structure and error conditions, which would make it more complete.

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?

The description adds meaningful information beyond the schema for most parameters: name is required, color is a hex example, kind and view_mode have allowed values listed, and group_id has extensive context about the workaround. A slight improvement would be to note defaults for color and view_mode.

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 'Create a new TickTick project (list).' It specifies the verb (create) and the resource (project), and it distinguishes from sibling tools like list_projects, update_project, delete_project by focusing on creation.

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?

The description provides a workflow hint ('Create project → manage_columns (for kanban) → create_task') and lists related tools. It does not explicitly state when not to use this tool, but the workflow and warnings about group_id offer sufficient guidance.

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/KpihX/tick-mcp'

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