Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

update_project_by_projectID

Modify an existing project's properties including name, color, view mode, kind, and sort order using its unique ID. Returns updated project details for task management.

Instructions

Update an existing project's properties. Requires project ID. Can modify name, color, view mode, kind and sort order. Returns updated project details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project to update (required)
nameNoNew name for the project
colorNoNew hex color code for the project
sortOrderNoUpdated sort order value
viewModeNoUpdated view mode: "list", "kanban", or "timeline"
kindNoUpdated project kind: "TASK" or "NOTE"

Implementation Reference

  • Handler for the 'update_project_by_projectID' tool. Validates input using throwValidError, constructs Project object from arguments, performs API POST to update project, and returns response as text content.
    case "update_project_by_projectID":{
        const project: Project = {
            id : args.projectId as string,
            name: args.name as string,
            ...(args.color ? { color: args.color as string } : {}),
            ...(args.sortOrder ? {sortOrder: args.sortOrder as number}:0),
            ...(args.viewMode ? {viewMode: args.viewMode as string}:{}),
            ...(args.kind ? {kind:args.kind as string}:{})
        };
        throwValidError(args.projectId as string,"1");
        const response: AxiosResponse = await dida365Api.post("/project", project);
    
        return {
            content: [
                {
                    type: "text",
                    text: `项目创建成功: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
  • Tool definition including name, description, and inputSchema for 'update_project_by_projectID' in the ListTools response, effectively registering the tool.
    {
        name: "update_project_by_projectID",
        description: "Update an existing project's properties. Requires project ID. Can modify name, color, view mode, kind and sort order. Returns updated project details.",
        inputSchema: {
            type: "object",
            properties: {
                projectId:{
                    type: "string",
                    description: "The ID of the project to update (required)"
                },
                name: {
                    type: "string",
                    description: "New name for the project"
                },
                color: {
                    type: "string",
                    description: "New hex color code for the project",
                },
                sortOrder:{
                    type:"integer",
                    description:"Updated sort order value"
                },
                viewMode:{
                    type:"string",
                    description:'Updated view mode: "list", "kanban", or "timeline"'
                },
                kind:{
                    type:"string",
                    description:'Updated project kind: "TASK" or "NOTE"'
                }
            },
            required: ["projectId"],
        },
    },
  • TypeScript interface definition for Project object used in the update_project_by_projectID handler.
    interface Project {
        id?: string;
        name?: string;
        color?: string;
        sortOrder?: number;
        viewMode? : string;
        kind? :string;
        closed?:boolean;
        groupId?: string;
        permission?:string;
    
    
    
    }
  • Helper function to validate projectId and taskId parameters, used in the tool 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 为空")
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that it 'Returns updated project details', which adds some context about output. However, it doesn't disclose critical behavioral traits such as permission requirements, whether changes are reversible, error handling, or side effects. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with two sentences that efficiently convey the core functionality and return value. Every sentence earns its place, though it could be slightly more structured by separating prerequisites from actions. No wasted words or redundancy.

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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on error conditions, authentication needs, rate limits, or what the 'updated project details' output entails. The description doesn't compensate for the absence of structured data, leaving gaps in understanding the tool's behavior.

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 all parameters thoroughly. The description lists modifiable fields (name, color, view mode, kind, sort order), which aligns with the schema but doesn't add meaningful semantics beyond what's in the schema descriptions. The baseline score of 3 is appropriate since the schema does the heavy lifting.

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 verb ('update') and resource ('existing project's properties'), making the purpose evident. It specifies what can be modified (name, color, view mode, kind, sort order), which helps distinguish it from sibling tools like 'update_task'. However, it doesn't explicitly differentiate from other update operations beyond listing modifiable fields.

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 mentions 'Requires project ID', which is a prerequisite but not a usage guideline. It doesn't provide guidance on when to use this tool versus alternatives like 'update_task' or 'create_project', nor does it specify scenarios where this tool is appropriate or inappropriate. No explicit when/when-not/alternatives are provided.

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