Skip to main content

​
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 isTeamFolder flag tells you whether the folder is a team (workspace-shared) folder or a private one.

​
Parameters

ParameterTypeRequiredDescription
noteGuidstringRequiredThe GUID of the note whose folders you want to list.

​
Response Format

{
  "content": [
    { "folderId": "12345", "name": "Project Discussion", "workspaceGuid": "ws_abc123", "isTeamFolder": true },
    { "folderId": "12346", "name": "Daily Standup", "workspaceGuid": "ws_abc123", "isTeamFolder": false }
  ],
  "total": 2
}
Field Descriptions:
FieldTypeDescription
content[]arrayThe folders the note belongs to. Empty when the note is not filed in any folder.
content[].folderIdstringStable folder identifier.
content[].namestringFolder name.
content[].workspaceGuidstringGUID of the workspace the folder belongs to. Always present (a note folder is always workspace-scoped).
content[].isTeamFolderbooleantrue for a team (workspace-shared) folder, false for a private folder.
totalnumberNumber of folders returned.
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: 
{
  "noteGuid": "note_abc123"
}
Response: 
{
  "content": [
    { "folderId": "200", "name": "Engineering", "workspaceGuid": "ws_abc123", "isTeamFolder": true }
  ],
  "total": 1
}

​
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.