Skip to main content

โ€‹
Overview

The four tools below change note titles and folder organization.
  • update_note โ€” Update a noteโ€™s title. Scope mcp:notes:write.
  • update_folder โ€” Update a folderโ€™s title, description, or color. Scope mcp:folders:write.
  • move_folder โ€” Move a folder under a different parent, or to the workspace root. Scope mcp:folders:write.
  • reorder_folders โ€” Reorder sibling folders within their parent. Scope mcp:folders:write.
When to use
  • Rename a note after its meeting so the title reflects what actually happened.
  • Rename a folder, tidy up its description, or recolor it for at-a-glance grouping.
  • Reorganize the folder tree: nest a folder under another, promote it to the workspace root, or change the order siblings appear in.
Account API key vs. workspace API key (folder tools). For update_folder, move_folder, and reorder_folders: an account API key can edit any folder it has edit access to (private or team). A workspace API key can edit only folders shared with all workspace members. Private folders and folders shared with just some members are rejected (see What notes a system API key reads). update_note works with account, workspace, or organization API keys.

โ€‹
update_note

Update a noteโ€™s title.

โ€‹
Parameters

โ€‹
Example

Request:
Response:

โ€‹
update_folder

Update a folderโ€™s title, description, and/or color. This is an AIP-134 field-mask update: only the fields you pass are changed, and everything you omit is left untouched. At least one field is required.

โ€‹
Parameters

At least one of title, description, or color must be provided. Fields you omit are not modified โ€” this lets you change the color without resending the title, for example.

โ€‹
Example

Request:
Response:

โ€‹
move_folder

Move a folder under a different parent, or to the workspace root.

โ€‹
Parameters

โ€‹
Example

Request:
Moves folder 12346 under folder 12345. Response:
To move a folder to the workspace root, omit newParentId (or pass null): Request:

โ€‹
reorder_folders

Reorder sibling folders. Pass the complete desired order of a single set of siblings; the workspace is inferred from the first folder ID.

โ€‹
Parameters

โ€‹
Example

Request:
Reorders the three sibling folders so they appear in the given order. Response:

โ€‹
Scope Requirements

update_note requires the mcp:notes:write scope; update_folder, move_folder, and reorder_folders require the mcp:folders:write scope.
API keys carry all scopes, so any valid API key can call these tools. The mcp:notes:write / mcp:folders:write scopes matter for OAuth-based clients, where the granted scopes gate which tools are callable.
Configure your API key at Tiro Platform API Keys.
  • get_note โ€” Read a noteโ€™s current metadata before updating its title.
  • Folder search โ€” Find a folderโ€™s folderId by name before editing, moving, or reordering it.
  • get_note_folders โ€” List the folders a note belongs to.