Skip to main content
Glama

folders

Destructive

List, create, move emails, get statistics, or delete to organize your mailbox.

Instructions

Manage mail folders. action=list (default) lists folders. action=create creates a folder. action=move moves emails between folders. action=stats gets folder counts for pagination planning. action=delete removes a folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction to perform (default: list)
includeItemCountsNoInclude counts of total and unread items (action=list)
includeChildrenNoInclude child folders in hierarchy (action=list)
nameNoName of the folder to create (action=create, required)
parentFolderNoParent folder name, default is root (action=create)
emailIdsNoComma-separated list of email IDs to move (action=move, required)
targetFolderNoFolder name to move emails to (action=move, required)
sourceFolderNoSource folder name, default is inbox (action=move)
folderNoFolder name (inbox, sent, drafts, etc.). Default: inbox (action=stats)
outputVerbosityNoOutput detail level (action=stats, default: standard)
folderIdNoFolder ID to delete (action=delete)
folderNameNoFolder name to delete — resolved to ID (action=delete). Cannot delete protected folders (Inbox, Drafts, Sent, etc.)
Behavior3/5

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

The description implicitly indicates that actions like 'delete' are destructive, consistent with annotations.destructiveHint=true. However, it does not disclose side effects (e.g., moving emails affects multiple folders) or error conditions beyond the schema. No contradictions with annotations.

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

Conciseness5/5

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

The description is extremely concise: two sentences. The first sentence states the purpose, the second enumerates actions with one-line summaries. Every word is useful, no redundancy.

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

Completeness3/5

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

Given 12 parameters and 5 actions, the description is minimal but covers the main actions. It lacks details on parameter interactions (e.g., includeItemCounts only for list) and return values (no output schema). Adequate but not thorough.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description lists actions but does not add new meaning beyond what the schema's parameter descriptions already provide. It does not explain conditional requirements (e.g., action=create requires name) which is already in the schema.

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

Purpose4/5

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

The description 'Manage mail folders' followed by a list of actions clearly indicates the tool's purpose. It distinguishes from sibling tools like 'send-email' or 'read-email' by focusing on folder management.

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

Usage Guidelines2/5

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

The description enumerates actions but does not provide guidance on when to use this tool versus other tools in the same server, such as 'access-shared-mailbox' or 'apply-category'. No exclusions or alternatives are mentioned.

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