Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

update_task

Modify an existing TickTick task by updating its title, description, due date, priority, or tags using the task ID.

Instructions

Update an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID to update (required)
titleNoNew task title
contentNoNew task description/content
dueDateNoNew due date in ISO format
priorityNoNew task priority (0=None, 1=Low, 3=Medium, 5=High)
tagsNoNew task tags

Implementation Reference

  • MCP tool handler for update_task: validates taskId presence and delegates to TickTickClient.updateTask, then returns success response with updated task JSON.
    case 'update_task':
      if (!args?.taskId) {
        throw new McpError(ErrorCode.InvalidParams, 'Task ID is required');
      }
      const updatedTask = await this.ticktickClient!.updateTask(args.taskId as string, args);
      return {
        content: [
          {
            type: 'text',
            text: `Task updated successfully: ${JSON.stringify(updatedTask, null, 2)}`,
          },
        ],
      };
  • Schema definition for the update_task tool, specifying input parameters including required taskId and optional fields like title, content, dueDate, priority, tags.
    {
      name: 'update_task',
      description: 'Update an existing task',
      inputSchema: {
        type: 'object',
        properties: {
          taskId: {
            type: 'string',
            description: 'Task ID to update (required)',
          },
          title: {
            type: 'string',
            description: 'New task title',
          },
          content: {
            type: 'string',
            description: 'New task description/content',
          },
          dueDate: {
            type: 'string',
            description: 'New due date in ISO format',
          },
          priority: {
            type: 'number',
            description: 'New task priority (0=None, 1=Low, 3=Medium, 5=High)',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'New task tags',
          },
        },
        required: ['taskId'],
      },
    },
  • Implementation of updateTask in TickTickClient: ensures authentication, makes POST request to /task/{taskId} API endpoint with updates, returns the updated task or throws error.
    async updateTask(taskId: string, updates: Partial<TickTickTask>): Promise<TickTickTask> {
      await this.ensureAuthenticated();
      
      try {
        const response = await this.client.post(`/task/${taskId}`, updates);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to update 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 the full burden of behavioral disclosure. While 'update' implies mutation, it doesn't specify whether this requires special permissions, if changes are reversible, what happens to unspecified fields, or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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 with zero waste. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly without unnecessary elaboration.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, error handling, or behavioral nuances. Given the complexity and lack of structured data, more context is needed for proper agent usage.

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, clearly documenting all 6 parameters with their types and purposes. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Update an existing task' clearly states the verb (update) and resource (task), but it's generic and doesn't distinguish this tool from similar operations like 'complete_task' or 'create_task'. It lacks specificity about what aspects can be updated or the scope of changes.

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?

No guidance is provided on when to use this tool versus alternatives like 'complete_task' or 'create_task'. The description doesn't mention prerequisites (e.g., needing an existing task ID) or contextual factors that would help an agent choose between sibling tools.

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