update_note
Modify or refresh existing notes in the Flint Note MCP server by updating content, metadata, or both, either individually or in batches, using identifiers and content hashes for precise changes.
Instructions
Update one or more existing notes
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | No | New content for the note - only used for single note update | |
| content_hash | No | Content hash of the current note for optimistic locking - required for single note update | |
| identifier | No | Note identifier in format "type/filename" or full path - only used for single note update | |
| metadata | No | Metadata fields to update - only used for single note update | |
| updates | No | Array of note updates (must specify content, metadata, or both) - used for batch updates | |
| vault_id | No | Optional vault ID to operate on. If not provided, uses the current active vault. |