Skip to main content
Glama
ZH1754629545

TickTick/Dida365 MCP Server

by ZH1754629545

update_task

Modify existing task properties like title, content, due date, priority, or status in TickTick/Dida365 task management systems.

Instructions

Modify an existing task's properties. Can update title, content, due date, priority or status. At least taskId is required. Returns the updated task details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe ID of the task to update (required)
titleNoNew title for the task
contentNoNew content/description for the task
dueDateNoNew due date in ISO 8601 format
priorityNoUpdated priority level (0-5)
statusNoTask completion status (0: incomplete, 1: complete)

Implementation Reference

  • The handler function for the 'update_task' tool. It extracts the taskId and optional update fields from arguments, constructs a Partial<Task> object, performs a PUT request to the Dida365 API at `/task/${taskId}`, and returns the response details.
    case "update_task": {
        const taskId = args.taskId as string;
        const updateData: Partial<Task> = {};
    
        if (args.title) updateData.title = args.title as string;
        if (args.content) updateData.content = args.content as string;
        if (args.dueDate) updateData.dueDate = args.dueDate as string;
        if (args.priority !== undefined) updateData.priority = args.priority as number;
        if (args.status !== undefined) updateData.status = args.status as number;
    
        const response: AxiosResponse = await dida365Api.put(`/task/${taskId}`, updateData);
    
        return {
            content: [
                {
                    type: "text",
                    text: `任务更新成功: ${JSON.stringify(response.data, null, 2)}`,
                },
            ],
        };
    }
  • The input schema definition for the 'update_task' tool, specifying required taskId and optional fields for updating task properties.
    name: "update_task",
    description: "Modify an existing task's properties. Can update title, content, due date, priority or status. At least taskId is required. Returns the updated task details.",
    inputSchema: {
        type: "object",
        properties: {
            taskId: {
                type: "string",
                description: "The ID of the task to update (required)",
            },
            title: {
                type: "string",
                description: "New title for the task",
            },
            content: {
                type: "string",
                description: "New content/description for the task",
            },
            dueDate: {
                type: "string",
                description: "New due date in ISO 8601 format",
            },
            priority: {
                type: "number",
                description: "Updated priority level (0-5)",
            },
            status: {
                type: "number",
                description: "Task completion status (0: incomplete, 1: complete)",
            },
        },
        required: ["taskId"],
    },
  • src/index.ts:170-203 (registration)
    Registration of the 'update_task' tool in the list of available tools returned by ListToolsRequestSchema, including name, description, and input schema.
    {
        name: "update_task",
        description: "Modify an existing task's properties. Can update title, content, due date, priority or status. At least taskId is required. Returns the updated task details.",
        inputSchema: {
            type: "object",
            properties: {
                taskId: {
                    type: "string",
                    description: "The ID of the task to update (required)",
                },
                title: {
                    type: "string",
                    description: "New title for the task",
                },
                content: {
                    type: "string",
                    description: "New content/description for the task",
                },
                dueDate: {
                    type: "string",
                    description: "New due date in ISO 8601 format",
                },
                priority: {
                    type: "number",
                    description: "Updated priority level (0-5)",
                },
                status: {
                    type: "number",
                    description: "Task completion status (0: incomplete, 1: complete)",
                },
            },
            required: ["taskId"],
        },
    },
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 discloses that the tool modifies properties and returns updated details, but lacks critical behavioral traits: it doesn't mention authentication needs, rate limits, whether updates are partial or overwrite all fields, error handling, or side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized with three sentences: first states purpose and updatable fields, second specifies required parameter, third describes return value. It's front-loaded with key information and avoids redundancy, though it could be slightly more structured (e.g., bullet points for fields). Every sentence adds value, making it efficient.

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 complexity (mutation tool with 6 parameters), no annotations, and no output schema, the description is incomplete. It lacks details on authentication, error cases, partial updates, and return format specifics. While it covers basic purpose and parameters, for a tool that modifies data, more behavioral and contextual information is needed to be fully helpful to an 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%, so the schema fully documents all 6 parameters (e.g., taskId as required, priority as 0-5, status as 0/1). The description adds minimal value beyond the schema by listing updatable fields (title, content, etc.) and noting taskId is required, but doesn't provide additional syntax, constraints, or examples. Baseline 3 is appropriate when 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 ('Modify') and resource ('existing task's properties'), specifying what fields can be updated (title, content, due date, priority, status). It distinguishes from sibling tools like 'create_task' (creation vs. modification) and 'delete_task' (deletion vs. update), though not explicitly named. The purpose is specific but could more directly contrast with alternatives.

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 by stating 'At least taskId is required,' which suggests prerequisites, but does not explicitly say when to use this tool versus alternatives like 'complete_task' (which might update status) or 'update_project_by_projectID' (for project-level changes). No explicit when-not-to-use guidance or named alternatives are provided, leaving usage context somewhat inferred.

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