Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

create_task

Add tasks to TickTick with title, description, due dates, priorities, and tags to organize your workflow.

Instructions

Create a new task in TickTick

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title (required)
contentNoTask description/content
projectIdNoProject ID where the task should be created
dueDateNoDue date in ISO format
priorityNoTask priority (0=None, 1=Low, 3=Medium, 5=High)
tagsNoTask tags

Implementation Reference

  • MCP tool handler for 'create_task': validates required title, calls TickTickClient.createTask with args, and returns success message with created task JSON.
    case 'create_task':
      if (!args?.title) {
        throw new McpError(ErrorCode.InvalidParams, 'Title is required');
      }
      const newTask = await this.ticktickClient!.createTask(args);
      return {
        content: [
          {
            type: 'text',
            text: `Task created successfully: ${JSON.stringify(newTask, null, 2)}`,
          },
        ],
      };
  • src/index.ts:90-124 (registration)
    Registration of 'create_task' tool in ListTools response, including name, description, and detailed input schema with properties and required fields.
    {
      name: 'create_task',
      description: 'Create a new task in TickTick',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Task title (required)',
          },
          content: {
            type: 'string',
            description: 'Task description/content',
          },
          projectId: {
            type: 'string',
            description: 'Project ID where the task should be created',
          },
          dueDate: {
            type: 'string',
            description: 'Due date in ISO format',
          },
          priority: {
            type: 'number',
            description: 'Task priority (0=None, 1=Low, 3=Medium, 5=High)',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Task tags',
          },
        },
        required: ['title'],
      },
    },
  • Input schema definition for 'create_task' tool specifying properties, types, descriptions, and required title field.
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Task title (required)',
          },
          content: {
            type: 'string',
            description: 'Task description/content',
          },
          projectId: {
            type: 'string',
            description: 'Project ID where the task should be created',
          },
          dueDate: {
            type: 'string',
            description: 'Due date in ISO format',
          },
          priority: {
            type: 'number',
            description: 'Task priority (0=None, 1=Low, 3=Medium, 5=High)',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Task tags',
          },
        },
        required: ['title'],
      },
    },
  • Core helper method in TickTickClient that authenticates and performs POST request to TickTick API /task endpoint to create a new task.
    async createTask(task: Partial<TickTickTask>): Promise<TickTickTask> {
      await this.ensureAuthenticated();
      
      try {
        const response = await this.client.post('/task', task);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to create task: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention authentication requirements, rate limits, whether tasks are immediately visible, or what happens on failure. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to quickly understand the core function.

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

Completeness2/5

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

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns a task ID, success confirmation), error conditions, or system constraints. Given the complexity of task management and lack of structured behavioral data, more context is needed.

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?

The input schema has 100% description coverage, thoroughly documenting all 6 parameters including required fields and priority values. The description adds no parameter information beyond what's in the schema, so it meets the baseline for high schema coverage but doesn't provide additional semantic context.

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?

The description clearly states the action ('Create a new task') and the target system ('in TickTick'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its sibling 'update_task' or explain when to create versus update, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_task' or 'complete_task', nor does it mention prerequisites such as needing a project ID for organization. It simply states what the tool does without contextual usage information.

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/rafliruslan/ticktick-mcp-server'

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