Skip to main content
Glama

update_email

Modify email properties such as read status, categories, and flags using specific email and account IDs. Integrates with Microsoft MCP server to streamline email management tasks.

Instructions

Update email properties (isRead, categories, flag, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
email_idYes
updatesYes

Implementation Reference

  • The main handler function for the 'update_email' tool. It uses the Microsoft Graph API to PATCH the specified email with the provided updates dictionary. Includes error handling if the request fails.
    @mcp.tool
    def update_email(
        email_id: str, updates: dict[str, Any], account_id: str
    ) -> dict[str, Any]:
        """Update email properties (isRead, categories, flag, etc.)"""
        result = graph.request(
            "PATCH", f"/me/messages/{email_id}", account_id, json=updates
        )
        if not result:
            raise ValueError(f"Failed to update email {email_id} - no response")
        return result
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('update') but doesn't specify whether this requires authentication, what permissions are needed, if changes are reversible, or any rate limits. The 'etc.' suggests additional properties can be updated, but the scope and effects are unclear, leaving significant gaps for a tool that modifies data.

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—a single sentence with no wasted words. It's front-loaded with the core action and examples, making it easy to scan. Every element ('update', 'email properties', examples) earns its place by conveying essential information efficiently.

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?

Given the complexity (a mutation tool with 3 parameters, nested objects, and no annotations or output schema), the description is incomplete. It lacks details on required permissions, error handling, return values, and parameter specifics. For a tool that modifies email data, this minimal description leaves too many operational questions unanswered, failing to provide adequate context 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?

Schema description coverage is 0%, so the description must compensate but adds minimal value. It mentions 'email properties' which loosely relates to the 'updates' parameter, but doesn't explain what 'account_id' or 'email_id' are, their formats, or the structure of 'updates' (e.g., key-value pairs). The description fails to clarify the three undocumented parameters, leaving semantics largely unexplained.

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 verb 'update' and resource 'email properties', listing specific examples like 'isRead, categories, flag'. It distinguishes from siblings like delete_email or move_email by focusing on property updates rather than deletion or relocation. However, it doesn't explicitly differentiate from other update tools like update_contact or update_event beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing email), exclusions (e.g., not for creating emails), or comparisons to siblings like modify_email or edit_email (though none exist in the list). It's a basic statement of function without contextual usage advice.

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