Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

copy_mails

Copy emails from your Naver Mail account to a different folder using mail UIDs and target folder name for organized mail management.

Instructions

메일을 다른 폴더로 복사

Input Schema

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

Implementation Reference

  • The implementation of the copy_mails tool logic that interacts with the mailbox client.
    def copy_mails(self, mail_uids: List[str], folder_name: str) -> None:
        """
        메일을 폴더로 복사합니다.
        """
        with self._get_mailbox_client() as mailbox:
            mailbox.copy(mail_uids, folder_name)
  • server.py:175-194 (registration)
    The MCP tool registration for 'copy_mails' including its input schema.
    Tool(
        name="copy_mails",
        description="메일을 다른 폴더로 복사",
        inputSchema={
            "type": "object",
            "properties": {
                "mail_uids": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "복사할 메일들의 UID 목록"
                },
                "folder_name": {
                    "type": "string",
                    "description": "복사할 대상 폴더 이름"
                }
            },
            "required": ["mail_uids", "folder_name"],
        }
    ),
    Tool(
  • The request handler logic that processes the 'copy_mails' tool call in server.py.
    elif name == "copy_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.copy_mails(mail_uids, folder_name)
        return [TextContent(type="text", text=f"{len(mail_uids)}개의 메일이 '{folder_name}' 폴더로 성공적으로 복사되었습니다.")]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('copy') but doesn't clarify whether this creates duplicates, preserves originals, requires specific permissions, or has side effects like updating timestamps. 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, direct sentence with zero wasted words. It front-loads the core action and resource efficiently, making it easy to parse quickly. Every word earns its place by contributing essential information.

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?

Given the tool's mutation nature (copying mails), lack of annotations, and absence of an output schema, the description is insufficient. It doesn't address behavioral traits, error conditions, or return values, leaving the agent with incomplete context for safe and effective use.

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 both parameters clearly documented in the schema itself. The description adds no additional semantic context beyond what the schema provides (e.g., format examples, constraints, or relationships between parameters). This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('copy') and resource ('mails to another folder'), making the purpose immediately understandable. It doesn't explicitly differentiate from the sibling 'move_mails' tool, which would be helpful for disambiguation, but the verb 'copy' is specific enough to convey the core function.

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?

The description provides no guidance on when to use this tool versus alternatives like 'move_mails' or other mail manipulation tools. It lacks context about prerequisites (e.g., needing valid mail UIDs and folder names) or typical use cases, leaving the agent to infer usage from the tool name alone.

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