Skip to main content
Glama

mark_email_as_read

Mark Outlook emails as read to manage your inbox by clearing unread notifications and organizing messages.

Instructions

Mark email as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
email_idYesEmail ID

Implementation Reference

  • Tool schema definition: input requires email_id string
    {
      name: "mark_email_as_read",
      description: "Mark email as read",
      inputSchema: {
        type: "object",
        properties: {
          email_id: {
            type: "string",
            description: "Email ID"
          }
        },
        required: ["email_id"]
      }
    },
  • MCP tool handler: validates input, calls outlookManager.markAsRead(emailId), returns success message
    case 'mark_email_as_read': {
      const emailId = (args as any)?.email_id;
      if (!emailId) {
        throw new Error('Email ID is required');
      }
      await outlookManager.markAsRead(emailId);
      return {
        content: [
          {
            type: 'text',
            text: `✅ **Email marked as read**\nEmail ID: ${emailId}`,
          },
        ],
      };
    }
  • Core implementation in OutlookManager: currently a no-op stub (Promise.resolve())
    async markAsRead(id: string): Promise<void> {
      return Promise.resolve();
    }
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 but offers minimal information. 'Mark email as read' implies a state mutation operation, but doesn't specify whether this requires specific permissions, whether the change is reversible, what happens if the email is already marked as read, or what side effects might occur. For a mutation tool with zero annotation coverage, this is inadequate.

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 with just three words that directly convey the core function. There's zero wasted language or unnecessary elaboration, making it efficiently front-loaded and easy to parse.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'read' means in context, whether the operation is idempotent, what permissions are required, or what the expected outcome looks like. Given the complexity of email state management and the lack of structured documentation, this description leaves critical gaps.

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?

The schema description coverage is 100% with the single parameter 'email_id' documented as 'Email ID'. The description adds no additional parameter information beyond what the schema already provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose2/5

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

The description 'Mark email as read' is essentially a tautology that restates the tool name without adding meaningful specificity. While it clearly indicates the action (marking) and resource (email), it doesn't distinguish this from potential sibling operations like 'mark_email_as_unread' or provide any context about what 'read' means in this system.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'get_email_by_id', 'get_inbox_emails', and various search functions, there's no indication of whether this should be used after retrieving an email, as part of a workflow, or what prerequisites might exist.

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/cqyefeng119/windows-outlook-mcp'

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