Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

delete_task

Remove a task from a TickTick/Dida365 project using its task ID and project ID. This action permanently deletes the specified task and returns a confirmation upon successful completion.

Instructions

Permanently delete a task from a project. Requires both task ID and project ID for confirmation. Returns success message upon deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe ID of the task to delete (required)
projectIdYesThe ID of the project containing the task (required)

Implementation Reference

  • Handler for the 'delete_task' tool: extracts taskId and projectId from arguments, validates them using throwValidError, deletes the task via dida365Api.delete, and returns a success message.
    case "delete_task": {
        const taskId = args.taskId as string;
        const projectId = args.projectId as string;
        throwValidError(projectId,taskId);
        await dida365Api.delete(`/project/${projectId}/task/${taskId}`);
    
        return {
            content: [
                {
                    type: "text",
                    text: `任务 ${taskId} 删除成功`,
                },
            ],
        };
    }
  • src/index.ts:204-221 (registration)
    Registration of the 'delete_task' tool including its name, description, and input schema definition in the tools array passed to the MCP server.
    {
        name: "delete_task",
        description: "Permanently delete a task from a project. Requires both task ID and project ID for confirmation. Returns success message upon deletion.",
        inputSchema: {
            type: "object",
            properties: {
                taskId: {
                    type: "string",
                    description: "The ID of the task to delete (required)",
                },
                projectId: {
                    type: "string",
                    description: "The ID of the project containing the task (required)"
                }
            },
            required: ["taskId","projectId"],
        },
    },
  • Helper validation function used in delete_task (and others) to ensure projectId and taskId are provided.
    function throwValidError(projectId : string,taskId : string){
        if(!projectId&&!taskId) throw new McpError(ErrorCode.InvalidRequest,"projectId 和 taskId 为空")
        if(!projectId) throw new McpError(ErrorCode.InvalidRequest,"projectId 为空")
        if(!taskId) throw new McpError(ErrorCode.InvalidRequest,"taskId 为空")
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the operation is permanent (destructive), requires confirmation via two IDs, and returns a success message. However, it lacks details on permissions, error handling, or side effects (e.g., impact on related data).

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 front-loaded with the core action, uses two efficient sentences with zero waste, and each sentence adds necessary information (purpose, requirements, and outcome). It is appropriately sized for a simple deletion tool.

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

Completeness3/5

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

Given the complexity (destructive operation with no annotations and no output schema), the description is adequate but has gaps. It covers the purpose, requirements, and outcome, but lacks details on permissions, error cases, or what the success message contains, which could be important for a deletion tool.

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%, so the schema already documents both parameters fully. The description adds minimal value beyond the schema by implying the parameters are for confirmation, but does not provide additional syntax or format details. This meets the baseline for high schema coverage.

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 the specific action ('permanently delete'), the resource ('a task'), and the context ('from a project'), distinguishing it from siblings like 'complete_task' or 'delete_project_by_projectID' which target different resources or operations.

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?

It provides clear context by specifying that both task ID and project ID are required for confirmation, which implies when to use it (when deleting a specific task within a project). However, it does not explicitly state when not to use it or name alternatives like 'complete_task' for non-destructive actions.

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/ZH1754629545/dida365-mcp-servers'

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