Skip to main content
Glama

folders

Destructive

List, create, delete mail folders; move emails between folders; retrieve folder counts for pagination planning.

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.)
Behavior2/5

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

Annotations already indicate destructiveHint=true for delete operations. The description merely restates actions from the schema (e.g., 'action=delete removes a folder') without adding behavioral details such as side effects (e.g., whether deleting a folder moves or removes its emails) or permission requirements. 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) and front-loaded with the core purpose. Every phrase is necessary; no redundancy or fluff. Structure is logical, listing actions in a clear progression.

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?

For a multi-action tool with 12 parameters and no output schema, the description lacks details on return values, error handling, or how to combine parameters with specific actions. However, the schema and action enum provide sufficient structure for a moderately experienced agent to infer usage.

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 coverage is 100%, so baseline is 3. The description adds no semantic information about parameters beyond what the schema provides (e.g., it does not explain that 'emailIds' is comma-separated or that 'folderName' cannot delete protected folders, though that is in the schema).

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 explicitly states 'Manage mail folders' and lists all five actions (list, create, move, stats, delete), clearly defining the tool's purpose and scope. It distinguishes itself from sibling tools like 'send-email' or 'manage-rules' by focusing solely on folder operations.

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 only enumerates actions without providing any guidance on when to use this tool versus alternatives, or when to choose one action over another. There is no mention of prerequisites, exclusions, or context for selecting specific actions.

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-mcp'

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