update_note
Modify the title or content of an existing note in TaskFlow MCP's task management system using the note's ID and request ID.
Instructions
Update an existing note's title or content.
Provide the 'requestId' and 'noteId', and optionally 'title' and/or 'content' to update.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| requestId | Yes | ||
| noteId | Yes | ||
| title | No | ||
| content | No |
Implementation Reference
- src/tools/TaskFlowTools.ts:630-633 (handler)The main handler function for the 'update_note' MCP tool. It destructures the input arguments and delegates the update logic to the TaskFlowService.updateNote method.async update_note(args: any) { const { requestId, noteId, title, content } = args ?? {}; return service.updateNote(String(requestId), String(noteId), { title, content }); },
- src/tools/TaskFlowTools.ts:368-383 (schema)Tool definition including name, description, and input schema for 'update_note'. This object is exported and used for registration.export const UPDATE_NOTE_TOOL: Tool = { name: "update_note", description: "Update an existing note's title or content.\n\n" + "Provide the 'requestId' and 'noteId', and optionally 'title' and/or 'content' to update.", inputSchema: { type: "object", properties: { requestId: { type: "string" }, noteId: { type: "string" }, title: { type: "string" }, content: { type: "string" }, }, required: ["requestId", "noteId"], }, };
- src/server/TaskFlowServer.ts:63-89 (registration)Registration of the UPDATE_NOTE_TOOL in the server's listTools handler, making it available via MCP protocol.this.server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: [ PLAN_TASK_TOOL, GET_NEXT_TASK_TOOL, MARK_TASK_DONE_TOOL, OPEN_TASK_DETAILS_TOOL, LIST_REQUESTS_TOOL, ADD_TASKS_TO_REQUEST_TOOL, UPDATE_TASK_TOOL, DELETE_TASK_TOOL, ADD_SUBTASKS_TOOL, MARK_SUBTASK_DONE_TOOL, UPDATE_SUBTASK_TOOL, DELETE_SUBTASK_TOOL, EXPORT_TASK_STATUS_TOOL, ADD_NOTE_TOOL, UPDATE_NOTE_TOOL, DELETE_NOTE_TOOL, ADD_DEPENDENCY_TOOL, GET_PROMPTS_TOOL, SET_PROMPTS_TOOL, UPDATE_PROMPTS_TOOL, REMOVE_PROMPTS_TOOL, ARCHIVE_COMPLETED_REQUESTS_TOOL, LIST_ARCHIVED_REQUESTS_TOOL, RESTORE_ARCHIVED_REQUEST_TOOL, ],
- The core service method implementing the note update logic: finds the note, applies updates with sanitization, updates timestamp, and persists changes.public async updateNote(requestId: string, noteId: string, updates: { title?: string; content?: string }) { await this.loadTasks(); const req = this.getRequest(requestId); if (!req) return { status: "error", message: "Request not found" }; if (!req.notes) return { status: "error", message: "No notes found for this request" }; const noteIndex = req.notes.findIndex((n) => n.id === noteId); if (noteIndex === -1) return { status: "error", message: "Note not found" }; const note = req.notes[noteIndex]; if (updates.title) note.title = sanitizeString(updates.title); if (updates.content) note.content = sanitizeString(updates.content); note.updatedAt = new Date().toISOString(); await this.saveTasks(); return { status: "note_updated", message: `Note ${noteId} has been updated.`, note }; }
- JSON schema definition for 'update_note' input validation in the shared schemas module (matches the tool's inputSchema).update_note: { type: "object", properties: { requestId: { type: "string" }, noteId: { type: "string" }, title: { type: "string" }, content: { type: "string" }, }, required: ["requestId", "noteId"], },