Skip to main content
Glama

delete_email

Remove unwanted emails from Outlook using the specified email and account IDs. Simplifies email management by enabling direct deletion through integrated Microsoft Graph API commands.

Instructions

Delete an email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
email_idYes

Implementation Reference

  • The 'delete_email' tool handler. Deletes the email by sending a DELETE request to Microsoft Graph API endpoint /me/messages/{email_id}. The @mcp.tool decorator handles registration and schema inference from type annotations.
    @mcp.tool
    def delete_email(email_id: str, account_id: str) -> dict[str, str]:
        """Delete an email"""
        graph.request("DELETE", f"/me/messages/{email_id}", account_id)
        return {"status": "deleted"}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete an email' implies a destructive, irreversible operation, but doesn't specify whether this is permanent deletion, moves to trash, requires specific permissions, or has confirmation steps. For a destructive operation with zero annotation coverage, this minimal description leaves critical behavioral questions unanswered.

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 maximally concise at three words, with zero wasted language. It's front-loaded with the core action and resource. While it's under-specified, this isn't a conciseness issue - every word earns its place by conveying essential information.

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

Completeness2/5

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

For a destructive operation with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't address critical context like: what happens after deletion, error conditions, permission requirements, or relationship to other email operations. The minimal description leaves too many unknowns for safe and effective use.

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

Parameters2/5

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

With 0% schema description coverage for both parameters, the description provides no information about what 'account_id' and 'email_id' represent, their format, or how to obtain them. The description mentions 'an email' but doesn't clarify the relationship between the two required parameters. For a tool with 2 undocumented parameters, the description fails to compensate for the schema coverage gap.

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

Purpose3/5

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

The description 'Delete an email' clearly states the action (delete) and resource (email), which is better than a tautology. However, it doesn't differentiate from sibling tools like 'delete_contact' or 'delete_event' - it only specifies the resource type without clarifying scope or constraints. The purpose is understandable but lacks specificity about what kind of email deletion this performs.

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 provides no guidance on when to use this tool versus alternatives. There are multiple email-related tools (get_email, move_email, update_email, search_emails) but no indication of when deletion is appropriate versus modification or retrieval. No prerequisites, constraints, or alternative suggestions 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

Related 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/elyxlz/microsoft-mcp'

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