Skip to main content
Glama

folders

Destructive

List, create, move emails between, and delete mail folders. Get folder statistics for inbox management.

Instructions

Manage mail folders (tool-level destructiveHint=true because delete permanently removes a folder; list and stats are read-only sub-actions despite the annotation). Folders can be addressed by name, by a slash-separated PATH for nested folders (e.g. Triage/Delete, Inbox/Clients/Acme, case-insensitive), or by explicit ID; list output includes each folder's full path and [id: …]. A bare name resolves a unique top-level folder first, then searches nested folders (ambiguous names return the candidates — disambiguate with a path or ID). action=list (default) returns the folder tree (toggle includeItemCounts for unread/total, includeChildren for hierarchy). action=create makes a new folder under the root, or under parentFolder (name/path) / parentFolderId, and returns its id. action=move relocates emails (emailIds) into targetFolder (name/path) or targetFolderId. action=stats returns counts (totalItemCount/unreadItemCount) for folder (name/path) or folderId, suitable for pagination planning. action=delete removes a folder (by folderName/path or folderId) and its contents — on Outlook.com the folder is moved to Deleted Items (recoverable until you empty it); M365/Exchange accounts may hard-delete per retention policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the folder to create (action=create, required)
actionNoAction to perform (default: list)
folderNoFolder name or path (inbox, sent, "Triage/Delete", etc.). Default: inbox (action=stats)
emailIdsNoComma-separated list of email IDs to move (action=move, required)
folderIdNoFolder ID (action=stats/delete)
folderNameNoFolder name or path to delete — resolved to ID (action=delete). Cannot delete protected folders (Inbox, Drafts, Sent, etc.)
parentFolderNoParent folder name or path (e.g. "Clients/Acme"); default is root (action=create)
sourceFolderNoSource folder name, default is inbox (action=move)
targetFolderNoDestination folder name or path, e.g. "Triage/Delete" (action=move; or use targetFolderId)
parentFolderIdNoParent folder ID — alternative to parentFolder for unambiguous targeting (action=create)
targetFolderIdNoDestination folder ID — alternative to targetFolder for unambiguous/nested targeting (action=move)
includeChildrenNoInclude child folders in hierarchy (action=list)
outputVerbosityNoOutput detail level (action=stats, default: standard)
includeItemCountsNoInclude counts of total and unread items (action=list)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond the annotations by detailing the destructive behavior of 'delete' (permanent removal, Outlook.com vs M365/Exchange differences) and clarifying that 'list' and 'stats' are read-only despite the destructiveHint annotation. It fully discloses behavioral traits with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is comprehensive and well-structured, starting with the core purpose and then systematically covering addressing, each action, and edge cases. While it is lengthy (multiple sentences), every sentence adds value; it could be slightly more streamlined but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters, 5 actions, no output schema, the description covers return values for list and stats (paths, IDs, counts), and for create (returns id). It lacks explicit return details for move and delete, but the behavior descriptions compensate. Overall, it is very informative and mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3, but the description adds substantial value: it explains the addressing system (name, path, ID), resolution rules for ambiguous names, provides examples like 'Triage/Delete', and clarifies parameter interdependencies across actions. This far exceeds what the schema alone offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Manage mail folders', clearly states the resource and the verb. It enumerates five distinct actions (list, create, move, stats, delete) and differentiates from sibling tools that handle other mail aspects (e.g., manage-rules, send-email). The scope is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use each action and how to address folders (name, path, ID). It explains default actions and resolution rules for ambiguous names. However, it does not explicitly state when not to use the tool or compare it to alternatives, though the sibling tools are sufficiently distinct.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/littlebearapps/outlook-assistant'

If you have feedback or need assistance with the MCP directory API, please join our Discord server