Skip to main content
Glama
shuakami

Mail MCP Tool

by shuakami

markAsUnread

Mark specific email messages as unread in your inbox to track them for follow-up or review. Use this tool to manage email status by providing the message UID and optional folder name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes
folderNoINBOX

Implementation Reference

  • MCP tool registration for 'markAsUnread', including Zod input schema {uid: number, folder?: string}, handler function that calls MailService.markAsUnread and returns formatted response.
    this.server.tool(
      "markAsUnread",
      {
        uid: z.number(),
        folder: z.string().default('INBOX')
      },
      async ({ uid, folder }) => {
        try {
          const numericUid = Number(uid);
          const success = await this.mailService.markAsUnread(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)}` }
            ]
          };
        }
      }
    );
  • MailService method that implements the core logic: opens IMAP box and removes the \\Seen flag from the specified email UID using delFlags.
    async markAsUnread(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.delFlags(numericUid, '\\Seen', (err) => {
            if (err) {
              reject(err);
              return;
            }
            resolve(true);
          });
        });
      });
    }
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