Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

create_folder

Create new email folders in your Naver Mail account to organize messages and improve inbox management.

Instructions

새 메일 폴더 생성

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_nameYes생성할 폴더 이름

Implementation Reference

  • The actual implementation of the folder creation logic using imap_tools mailbox.folder.create.
    def create_folder(self, folder_name: str) -> None:
        """
        폴더를 생성합니다.
        """
        with self._get_mailbox_client() as mailbox:
            mailbox.folder.create(folder_name)
  • server.py:109-122 (registration)
    The Tool definition for create_folder in the MCP server list_tools.
    Tool(
        name="create_folder",
        description="새 메일 폴더 생성",
        inputSchema={
            "type": "object",
            "properties": {
                "folder_name": {
                    "type": "string",
                    "description": "생성할 폴더 이름"
                }
            },
            "required": ["folder_name"],
        }
    ),
  • The MCP tool handler that invokes MailService.create_folder when the 'create_folder' tool is called.
    elif name == "create_folder":
        folder_name = args.get("folder_name")
        if not folder_name:
            return [TextContent(type="text", text="폴더 이름이 필요합니다.")]
    
        mail_service.create_folder(folder_name)
        return [TextContent(type="text", text=f"폴더 '{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 ('create') but does not cover critical aspects like required permissions, whether the operation is idempotent, error conditions, or effects on existing data. This leaves significant gaps for a mutation tool.

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 purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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 is a mutation operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, or return values, which are essential for an agent to use the tool effectively in context.

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 input schema has 100% description coverage, with the parameter 'folder_name' clearly documented. The description does not add any extra semantic meaning beyond what the schema provides, such as naming constraints or examples, so it meets 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 '새 메일 폴더 생성' (Create new mail folder) clearly states the verb ('create') and resource ('mail folder'), making the purpose evident. However, it does not differentiate from sibling tools like 'rename_folder', which also modifies folders, leaving room for improvement in specificity.

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. It lacks context such as prerequisites (e.g., permissions), exclusions, or comparisons to related tools like 'list_folders' or 'rename_folder', leaving the agent without usage direction.

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