Skip to main content
Glama

folders

Destructive

Organize Outlook emails by managing folders: list, create, move emails between folders, get statistics, or delete folders to maintain an efficient inbox structure.

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

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

The description adds valuable behavioral context beyond annotations. While annotations indicate destructiveHint=true and readOnlyHint=false, the description clarifies which specific actions are destructive (delete) versus non-destructive (list, stats), and mentions constraints like 'Cannot delete protected folders'. This provides practical operational guidance that annotations alone don't convey.

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 efficiently structured with zero wasted words. It uses a single sentence that clearly enumerates all five actions with their purposes, making it easy to scan and understand. Every phrase earns its place by conveying essential information about the tool's capabilities.

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?

For a multi-action tool with 12 parameters and no output schema, the description provides good coverage of the tool's scope and actions. It mentions key behavioral constraints (protected folders) and action purposes. However, it doesn't address potential side effects, error conditions, or what happens with empty/missing parameters across different actions.

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?

With 100% schema description coverage, the schema already documents all 12 parameters thoroughly. The description doesn't add significant parameter semantics beyond what's in the schema - it mentions action types but doesn't provide additional syntax, format, or constraint details for parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool's purpose as managing mail folders with specific actions (list, create, move, stats, delete). It provides a verb+resource combination but doesn't explicitly differentiate from sibling tools like 'manage-category' or 'mailbox-settings' that might also handle folder-related operations.

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

Usage Guidelines3/5

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

The description implies usage context by listing actions, but doesn't provide explicit guidance on when to choose this tool versus alternatives like 'manage-category' or 'mailbox-settings'. It mentions default actions but lacks clear when/when-not criteria or prerequisites for different operations.

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