Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

complete_task

Mark tasks as completed in TickTick by providing task and project IDs to update task status and track progress.

Instructions

Mark a task as completed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID to complete (required)
projectIdYesProject ID containing the task (required)

Implementation Reference

  • MCP tool handler for 'complete_task': validates taskId and projectId, delegates to TickTickClient.completeTask, returns formatted response with task details.
    case 'complete_task':
      if (!args?.taskId || !args?.projectId) {
        throw new McpError(ErrorCode.InvalidParams, 'Task ID and Project ID are required');
      }
      const completedTask = await this.ticktickClient!.completeTask(args.taskId as string, args.projectId as string);
      return {
        content: [
          {
            type: 'text',
            text: `Task completed successfully: ${JSON.stringify(completedTask, null, 2)}`,
          },
        ],
      };
  • src/index.ts:178-195 (registration)
    Tool registration in ListTools handler: defines name, description, and input schema requiring taskId and projectId.
    {
      name: 'complete_task',
      description: 'Mark a task as completed',
      inputSchema: {
        type: 'object',
        properties: {
          taskId: {
            type: 'string',
            description: 'Task ID to complete (required)',
          },
          projectId: {
            type: 'string',
            description: 'Project ID containing the task (required)',
          },
        },
        required: ['taskId', 'projectId'],
      },
    },
  • TickTickClient helper method: ensures authentication and makes POST request to TickTick API to mark task as complete.
    async completeTask(taskId: string, projectId: string): Promise<TickTickTask> {
      await this.ensureAuthenticated();
      
      try {
        const response = await this.client.post(`/project/${projectId}/task/${taskId}/complete`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to complete 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. While 'Mark as completed' implies a mutation, it doesn't specify if this is reversible, requires specific permissions, affects task dependencies, or what happens upon completion (e.g., notifications, status changes). This leaves significant gaps for a mutation tool.

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 function with zero wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects like side effects, error conditions, or return values, leaving the agent with incomplete context for proper invocation.

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 schema description coverage is 100%, with both parameters clearly documented in the schema. The description adds no additional meaning beyond the schema's parameter descriptions, so it meets the baseline score of 3 without compensating or enhancing parameter understanding.

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 ('Mark as completed') and resource ('a task'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_task' which might also handle task completion, so it doesn't reach the highest 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 'delete_task', nor does it mention prerequisites or context for completion. It simply states what the tool does without usage context.

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