Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

delete_task

Remove a task from TickTick task management by specifying its task ID and project ID to maintain organized workflows.

Instructions

Delete a task

Input Schema

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

Implementation Reference

  • Core handler function that authenticates and makes the API DELETE request to remove the task from the specified project.
    async deleteTask(taskId: string, projectId: string): Promise<void> {
      await this.ensureAuthenticated();
      
      try {
        await this.client.delete(`/project/${projectId}/task/${taskId}`);
      } catch (error) {
        throw new Error(`Failed to delete task: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • MCP server handler for the delete_task tool, which validates input parameters and calls the TickTickClient's deleteTask method.
    case 'delete_task':
      if (!args?.taskId || !args?.projectId) {
        throw new McpError(ErrorCode.InvalidParams, 'Task ID and Project ID are required');
      }
      await this.ticktickClient!.deleteTask(args.taskId as string, args.projectId as string);
      return {
        content: [
          {
            type: 'text',
            text: 'Task deleted successfully',
          },
        ],
      };
  • src/index.ts:161-177 (registration)
    Registration of the delete_task tool in the ListTools handler, defining name, description, and input schema.
      name: 'delete_task',
      description: 'Delete a task',
      inputSchema: {
        type: 'object',
        properties: {
          taskId: {
            type: 'string',
            description: 'Task ID to delete (required)',
          },
          projectId: {
            type: 'string',
            description: 'Project ID containing the task (required)',
          },
        },
        required: ['taskId', 'projectId'],
      },
    },
  • Input schema definition for the delete_task tool, specifying required taskId and projectId parameters.
    inputSchema: {
      type: 'object',
      properties: {
        taskId: {
          type: 'string',
          description: 'Task ID to delete (required)',
        },
        projectId: {
          type: 'string',
          description: 'Project ID containing the task (required)',
        },
      },
      required: ['taskId', 'projectId'],
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete a task' but doesn't disclose if deletion is permanent, reversible, requires specific permissions, has side effects (e.g., cascading deletions), or rate limits. This is inadequate 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 extremely concise with 'Delete a task'—a single, front-loaded sentence that wastes no words. It efficiently conveys the core action, though this brevity contributes to gaps in other dimensions.

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 deletion tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., permanence, permissions), usage context relative to siblings, and output expectations, making it insufficient for safe and effective use by an AI agent.

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 100%, with both parameters documented in the schema. The description adds no meaning beyond the schema, which already specifies 'taskId' and 'projectId' as required. Baseline 3 is appropriate as 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 'Delete a task' states the action and resource but is vague about scope and lacks sibling differentiation. It specifies the verb 'Delete' and resource 'task', but doesn't clarify if it's permanent deletion, soft deletion, or how it differs from alternatives like 'complete_task' or 'update_task'.

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. With siblings like 'complete_task' and 'update_task' available, the description doesn't indicate scenarios for deletion over completion or modification, nor does it mention prerequisites or exclusions.

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