Overview
get_note_folders is a reverse lookup: given a note’s GUID, it returns the folders that note belongs to. Use it to answer “which folder(s) is this note in?” — the inverse of list_notes with filter.folderId (which lists the notes inside a folder).
This is distinct from the folder-search tools. Reach for search_private_folders / search_team_folders when you want to browse or search the folder tree by name; reach for get_note_folders when you already have a note and want its folder membership.
Primary use cases:
- Show where a note lives (“This note is filed under Engineering > Q1 Planning”).
- Decide which folder-search tool to follow up with: each result’s
isTeamFolderflag tells you whether the folder is a team (workspace-shared) folder or a private one.
Parameters
Response Format
The folder list is access-filtered server-side: only folders reachable by the caller (via the note’s workspace and the caller’s membership) are returned.
Usage Example
Request:Scope Requirements
get_note_folders requires both the mcp:notes:read and mcp:folders:read scopes — it is keyed by an accessible note (notes scope) but returns folder metadata (folders scope, the same scope the search_*_folders tools require). Access is additionally gated by note access: a caller who cannot read the note cannot list its folders. API keys already include all scopes; OAuth tokens must be granted both. Configure your API key at Tiro Platform API Keys.
Related Tools
list_notes— The forward direction: list the notes inside a folder viafilter.folderId.get_note— Get the note’s own metadata and content.search_private_folders/search_team_folders— Search the folder tree by name when you don’t already have a note.