Skip to main content
Glama
marlonluo2018

Microsoft Graph MCP Server

manage_emails

Organize your inbox by moving, deleting, archiving, flagging, or categorizing emails. Supports individual and batch actions for efficient email management.

Instructions

Manage emails with multiple actions. Supports moving, deleting, archiving, flagging, and categorizing emails. Actions include: move_single, move_all, delete_single, delete_multiple, delete_all, archive_single, archive_multiple, flag_single, flag_multiple, categorize_single, categorize_multiple. Returns: {success: boolean, message: string, moved_count: integer, failed_count: integer, errors: array}. Note: Invalid cache_number returns appropriate error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'move_single' to move a single email, 'move_all' to move all emails from a folder, 'delete_single' to delete a single email, 'delete_multiple' to delete multiple emails in ONE batch call (provide cache_numbers array with all items), 'delete_all' to delete all emails from a folder, 'archive_single' to archive a single email, 'archive_multiple' to archive multiple emails in ONE batch call, 'flag_single' to flag a single email, 'flag_multiple' to flag multiple emails in ONE batch call, 'categorize_single' to categorize a single email, 'categorize_multiple' to categorize multiple emails in ONE batch call
categoriesNoList of category names to apply (e.g., ['Important', 'Work']). Required for 'categorize_single' and 'categorize_multiple' actions
flag_statusNoFlag status: 'flagged' to mark as flagged, 'complete' to mark as complete. Required for 'flag_single' and 'flag_multiple' actions
cache_numberNoCache number from browse_email_cache (e.g., 1, 2, 3). Required for 'move_single', 'delete_single', 'archive_single', 'flag_single', and 'categorize_single' actions
cache_numbersNoList of cache numbers from browse_email_cache (e.g., [1, 2, 3]). Required for 'delete_multiple', 'archive_multiple', 'flag_multiple', and 'categorize_multiple' actions. IMPORTANT: Pass ALL cache numbers in a SINGLE call - do NOT call multiple times for individual items
source_folderNoSource folder path (e.g., 'Inbox', 'Archive/2024'). Required for 'move_all' and 'delete_all' actions
destination_folderNoDestination folder path (e.g., 'Archive/2024', 'Inbox/Projects'). Required for 'move_single' and 'move_all' actions
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It specifies the return structure ({success, message, moved_count, etc.}) and notes error behavior for invalid cache_number, but lacks disclosure of side effects (e.g., permanence of deletes, folder creation needs) or authorization requirements.

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

Conciseness3/5

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

The description is moderately sized with a clear structure (actions list, return info, note), but it repeats the action list already present in the schema enums, making it slightly verbose.

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 the tool's complexity (7 parameters, 11 actions) and no output schema, the description provides return structure and an error note, but lacks context on prerequisites (e.g., dependency on browse_email_cache for cache numbers), batch operation implications, or side effects of actions like deletion.

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% with detailed parameter descriptions, so baseline is 3. The description adds the return structure and a note about invalid cache_number errors, but does not augment parameter meaning beyond 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 starts with 'Manage emails with multiple actions' and explicitly lists all supported actions (move, delete, archive, flag, categorize), clearly distinguishing the tool from siblings like send_email or search_emails which serve different purposes.

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 does not explicitly state when to use this tool versus alternatives like search_emails or browse_email_cache; usage is implied by the listed actions but no guidance on exclusions or prerequisites is provided.

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/marlonluo2018/microsoft_graph_mcp_server'

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