Skip to main content
Glama
Leonamin

Naver Mail MCP Server

by Leonamin
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

delete_mails

Remove selected emails from your Naver Mail account by specifying their unique identifiers. This tool helps manage your inbox by permanently deleting unwanted messages.

Instructions

메일 삭제

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mail_uidsYes삭제할 메일들의 UID 목록

Implementation Reference

  • service/mail_service.py:108-113 (handler)
    The `delete_mails` method within the `MailService` class implements the actual logic to delete emails using the `imap_tools` library.
    def delete_mails(self, mail_uids: List[str]) -> None:
    """
    메일을 삭제합니다.
    """
    with self._get_mailbox_client() as mailbox:
        mailbox.delete(mail_uids)

Tool Definition Quality

D1.7/5.0
Behavior1/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. '메일 삭제' only states the action without revealing critical traits: whether deletion is permanent or reversible, if it requires specific permissions, what happens on success/failure, or any rate limits. This is inadequate for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise with just two words, this is under-specification rather than effective brevity. The description fails to front-load essential information and doesn't earn its place by adding value beyond the tool name. It lacks structure for a tool with significant implications.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is severely incomplete. It doesn't address behavioral aspects, error handling, or usage context, leaving the agent with insufficient information to invoke this tool safely and correctly.

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 as an array of strings for UIDs of mails to delete. The description adds no additional parameter semantics beyond what the schema provides, 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.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '메일 삭제' (delete mails) restates the tool name without adding specificity. It doesn't distinguish this tool from sibling tools like 'delete_folder' or 'move_mails' that also involve deletion operations. While the verb and resource are clear, this is essentially a tautology of the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 mail UIDs from list operations), exclusions (e.g., not for folders), or comparisons to siblings like 'move_mails' for archiving instead of deletion.

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