Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

move_mails

Move emails between folders in your Naver Mail account. Specify mail UIDs and target folder name to organize your inbox efficiently.

Instructions

메일을 다른 폴더로 이동

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mail_uidsYes이동할 메일들의 UID 목록
folder_nameYes이동할 대상 폴더 이름

Implementation Reference

  • The actual business logic that performs the mail moving operation in the mail service.
    def move_mails(self, mail_uids: List[str], folder_name: str) -> None:
        """
        메일을 폴더로 이동합니다.
        """
        with self._get_mailbox_client() as mailbox:
            mailbox.move(mail_uids, folder_name)
  • The handler logic in the MCP server that extracts arguments and calls the mail service to move mails.
    elif name == "move_mails":
        mail_uids = args.get("mail_uids", [])
        folder_name = args.get("folder_name")
    
        if not mail_uids or not folder_name:
            return [TextContent(type="text", text="메일 UID 목록과 폴더 이름이 필요합니다.")]
    
        # 폴더 존재 여부 확인
        if not mail_service.is_folder_exists(folder_name):
            return [TextContent(type="text", text=f"폴더 '{folder_name}'가 존재하지 않습니다.")]
    
        mail_service.move_mails(mail_uids, folder_name)
        return [TextContent(type="text", text=f"{len(mail_uids)}개의 메일이 '{folder_name}' 폴더로 성공적으로 이동되었습니다.")]
  • server.py:156-168 (registration)
    MCP Tool registration for 'move_mails' with its input schema.
    Tool(
        name="move_mails",
        description="메일을 다른 폴더로 이동",
        inputSchema={
            "type": "object",
            "properties": {
                "mail_uids": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "이동할 메일들의 UID 목록"
                },
                "folder_name": {
                    "type": "string",
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. While 'move' implies mutation, it doesn't specify whether this is reversible, what permissions are required, what happens to the original mails, or error handling. The description lacks critical behavioral context for a mutation operation.

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 with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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 happens after moving (are mails removed from source?), what the response looks like, error conditions, or how this differs from copying. More context is needed for proper tool understanding.

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%, so the schema already documents both parameters completely. The description doesn't add any additional meaning about the parameters beyond what's in the schema descriptions, 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 ('move') and resource ('mails to another folder'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling 'copy_mails' tool, which performs a similar operation with different semantics.

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 about when to use this tool versus alternatives like 'copy_mails' or 'delete_mails'. The description doesn't mention prerequisites, error conditions, or appropriate contexts for moving versus copying mails.

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