Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

delete_project_by_projectID

Permanently delete a TickTick/Dida365 project and all its tasks using the project ID. This action removes the project and its contents from your task management system.

Instructions

Permanently delete a project by its ID. This will also delete all tasks within the project. Returns success message upon deletion.

Input Schema

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

Implementation Reference

  • The core handler logic for the 'delete_project_by_projectID' tool. It extracts the projectId from arguments, validates it using throwValidError helper, performs a DELETE request to the Dida365 API endpoint `/project/${projectId}`, and returns a success message with the API response data.
    case "delete_project_by_projectID":{
        const projectId:string = args.projectId as string;
        throwValidError(projectId,"1");
    
        const response: AxiosResponse = await dida365Api.delete(`/project/${projectId}`);
        return {
            content: [
                {
                    type: "text",
                    text: `删除项目成功: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
    }
  • The input schema definition for the 'delete_project_by_projectID' tool, specifying that it requires a 'projectId' string parameter.
    inputSchema: {
        type: "object",
        properties: {
            projectId:{
                type: "string",
                description: "The ID of the project to delete (required)"
            }
        },
        required: ["projectId"],
    },
  • src/index.ts:327-340 (registration)
    The tool registration entry in the ListTools response, defining the name, description, and input schema for 'delete_project_by_projectID'.
    {
        name: "delete_project_by_projectID",
        description: "Permanently delete a project by its ID. This will also delete all tasks within the project. Returns success message upon deletion.",
        inputSchema: {
            type: "object",
            properties: {
                projectId:{
                    type: "string",
                    description: "The ID of the project to delete (required)"
                }
            },
            required: ["projectId"],
        },
    }
  • Helper function used for input validation in the handler (and others). Checks if projectId and/or taskId are provided, throwing McpError if missing. Called with dummy taskId '1' in this tool's handler.
    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 为空")
    }
Behavior4/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, it cascades to delete all tasks within the project, and it returns a success message. However, it doesn't cover permissions, error conditions, or confirmation requirements.

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?

Two sentences with zero waste: first states the action and consequences, second states the return. Front-loaded with the core purpose, appropriately sized for a single-parameter destructive operation.

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?

For a destructive tool with no annotations and no output schema, the description covers the permanence and cascade effect adequately but lacks details on permissions, error handling, or what the success message contains. It's minimally viable but has clear gaps.

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%, so the schema already documents the projectId parameter fully. The description doesn't add any meaning beyond what the schema provides, such as format examples or ID sourcing. Baseline 3 is appropriate when schema does the heavy lifting.

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 project'), and the method ('by its ID'). It distinguishes from siblings like delete_task by specifying it deletes projects, not tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing to delete a project and its tasks, but doesn't explicitly state when to use this vs. alternatives like update_project_by_projectID or warn against accidental deletion. It mentions the cascade effect on tasks, which provides some 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/ZH1754629545/dida365-mcp-servers'

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