Skip to main content
Glama
shuakami

Mail MCP Tool

by shuakami

markAsRead

Mark email messages as read in your inbox using their unique identifiers. This tool helps manage email notifications and organize your mailbox by updating message status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes
folderNoINBOX

Implementation Reference

  • Core implementation of markAsRead in MailService class. Connects to IMAP, opens the specified folder, and adds the '\Seen' flag to the email UID to mark it as read.
    async markAsRead(uid: number | string, folder: string = 'INBOX'): Promise<boolean> {
      await this.connectImap();
      
      // 确保 uid 为数字类型
      const numericUid = typeof uid === 'string' ? parseInt(uid, 10) : uid;
    
      return new Promise((resolve, reject) => {
        this.imapClient.openBox(folder, false, (err) => {
          if (err) {
            reject(err);
            return;
          }
    
          this.imapClient.addFlags(numericUid, '\\Seen', (err) => {
            if (err) {
              reject(err);
              return;
            }
            resolve(true);
          });
        });
      });
    }
  • Registration of the 'markAsRead' MCP tool. Defines input schema using Zod (uid: number, folder: string default 'INBOX') and a wrapper handler that delegates to MailService.markAsRead and formats the response.
    "markAsRead",
    {
      uid: z.number(),
      folder: z.string().default('INBOX')
    },
    async ({ uid, folder }) => {
      try {
        const numericUid = Number(uid);
        const success = await this.mailService.markAsRead(numericUid, folder);
        
        if (success) {
          return {
            content: [
              { type: "text", text: `邮件(UID: ${uid})已标记为已读` }
            ]
          };
        } else {
          return {
            content: [
              { type: "text", text: `标记邮件(UID: ${uid})为已读失败` }
            ]
          };
        }
      } catch (error) {
        return {
          content: [
            { type: "text", text: `标记邮件为已读时发生错误: ${error instanceof Error ? error.message : String(error)}` }
          ]
        };
      }
    }
  • Zod schema defining input parameters for the markAsRead tool: uid (number, required) and folder (string, defaults to 'INBOX').
    {
      uid: z.number(),
      folder: z.string().default('INBOX')
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/shuakami/mcp-mail'

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