Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

mark_mails_unimportant

Change emails to unimportant status in Naver Mail to reduce inbox clutter and prioritize important messages. Specify email UIDs to mark as low priority.

Instructions

메일을 중요하지 않음 상태로 변경

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mail_uidsYes중요하지 않음 처리할 메일들의 UID 목록

Implementation Reference

  • The actual implementation of the tool 'mark_mails_unimportant' inside MailService.
    def mark_as_unimportant(self, mail_uids: List[str]) -> None:
        """
        메일을 중요 상태로 변경합니다.
        중요 상태는 메일 클라이언트에서 중요 표시로 표시됩니다.
        """
        with self._get_mailbox_client() as mailbox:
            mailbox.flag(mail_uids, '\\Flagged', False)
  • server.py:484-492 (registration)
    The tool handler registration and invocation logic in the server.
    elif name == "mark_mails_unimportant":
        mail_uids = args.get("mail_uids", [])
    
        if not mail_uids:
            return [TextContent(type="text", text="중요하지 않음 처리할 메일 UID 목록이 필요합니다.")]
    
        mail_service.mark_as_unimportant(mail_uids)
        return [TextContent(type="text", text=f"{len(mail_uids)}개의 메일이 중요하지 않음 상태로 변경되었습니다.")]
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the state change but doesn't disclose whether this is reversible, if it affects mail visibility/filtering, permission requirements, or side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It is appropriately sized for a simple state-change operation and front-loads the core action.

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 insufficient. It doesn't explain what 'unimportant' means operationally, whether the change is persistent, what the response looks like, or error conditions. Given the complexity of modifying mail states and lack of structured data, more context is needed.

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?

Schema description coverage is 100%, with the parameter 'mail_uids' clearly documented in the schema as '중요하지 않음 처리할 메일들의 UID 목록' (list of UIDs of mails to mark unimportant). The description adds no additional parameter context beyond what the schema provides, meeting the baseline for high schema coverage.

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 action ('중요하지 않음 상태로 변경' - change to unimportant status) and resource ('메일' - mails), making the purpose understandable. It distinguishes from siblings like 'mark_mails_important' by specifying the opposite state, but doesn't explicitly contrast with other mail-modification tools like 'mark_mails_read' or 'delete_mails'.

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, appropriate contexts, or when not to use it (e.g., vs. deleting or archiving mails). It relies solely on the tool name and description for implicit differentiation.

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/Leonamin/NaverMail-MCP-Server'

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