Problem
Currently, slite_update_note requires the markdown parameter even when only updating the title. This forces users to:
- Fetch the full note content first
- Send the entire body back just to change the title
This is inefficient and error-prone for simple rename operations.
Current Behavior
required: ["noteId", "markdown"]
title: optional
Proposed Solution
Make markdown optional in slite_update_note. If not provided, only update the title while preserving existing content.
required: ["noteId"]
// At least one of title or markdown should be provided
Use Case
Renaming weekly notes from inconsistent naming to standardized format:
| Current Name |
New Name |
| Week of Dec 22, 2025 |
2025 - W52 - Dec 22 |
| weekly update 29 dec |
2026 - W01 - Dec 29 |
| Week of Jan 6, 2026 |
2026 - W02 - Jan 5 |
Currently this simple rename requires fetching and re-sending the full markdown body for each note.
Problem
Currently,
slite_update_noterequires themarkdownparameter even when only updating the title. This forces users to:This is inefficient and error-prone for simple rename operations.
Current Behavior
Proposed Solution
Make
markdownoptional inslite_update_note. If not provided, only update the title while preserving existing content.Use Case
Renaming weekly notes from inconsistent naming to standardized format:
Currently this simple rename requires fetching and re-sending the full markdown body for each note.