Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin

rename_folder

Change the name of a mail folder in your Naver Mail account. Specify the current folder name and the new name to update it.

Instructions

메일 폴더 이름 변경

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
old_folder_nameYes기존 폴더 이름
new_folder_nameYes새 폴더 이름

Implementation Reference

  • The rename_folder method in MailService implements the tool logic by using the imap_tools library to rename a mail folder.
    def rename_folder(self, old_folder_name: str, new_folder_name: str) -> None:
        """
        폴더 이름을 변경합니다.
        """
        with self._get_mailbox_client() as mailbox:
            mailbox.folder.rename(old_folder_name, new_folder_name)
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. It states the action (rename) but doesn't mention permissions required, whether the operation is reversible, potential side effects, error conditions, or what happens if the new name conflicts. This is a significant gap 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 phrase that directly states the tool's purpose with zero wasted words. It's appropriately sized and immediately communicates 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 the tool returns, error handling, or behavioral constraints. The agent would need to guess about important aspects of using this tool.

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 both parameters clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline for high schema coverage without providing extra value.

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 '메일 폴더 이름 변경' (Mail folder rename) clearly states the verb (rename/change) and resource (mail folder). It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'create_folder' or 'delete_folder' beyond the obvious action difference.

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 doesn't mention prerequisites (e.g., needing an existing folder), exclusions, or comparisons to sibling tools like 'create_folder' or 'delete_folder' that also manipulate folders.

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