Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

create_mailbox

Create a new mailbox folder in an IMAP email account to organize messages. Use this tool to add custom folders for better email management.

Instructions

Create a new mailbox folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mailboxYesNew mailbox name

Implementation Reference

  • The actual implementation of the create_mailbox logic which uses the underlying client's create_folder method.
    def create_mailbox(self, mailbox: str) -> bool:
        """Create a new mailbox folder."""
        self._ensure_connected()
        self.client.create_folder(mailbox)
        return True
  • Registration of the 'create_mailbox' tool with its schema definition in the MCP server.
    make_tool(
        "create_mailbox",
        "Create a new mailbox folder",
        {
            "mailbox": {"type": "string", "description": "New mailbox name"},
        },
        ["mailbox"],
    ),
  • Dispatch logic in the server handling the 'create_mailbox' tool request by calling the client method.
    elif name == "create_mailbox":
        return imap_client.create_mailbox(args["mailbox"])
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 'Create' implies a write operation, it doesn't specify permission requirements, whether the operation is idempotent, what happens on duplicate names, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple tool with one parameter and gets straight to the point.

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 creation (e.g., success/failure response, whether the new mailbox becomes selected), doesn't mention potential constraints or side effects, and provides no context about the broader mailbox system.

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 has 100% description coverage, with the single parameter 'mailbox' clearly documented as 'New mailbox name'. The description adds no additional parameter context beyond what's already in the schema, which meets the baseline expectation when schema coverage is complete.

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 ('Create') and resource ('new mailbox folder'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'list_mailboxes' or 'select_mailbox', but the verb+resource combination is specific enough for basic understanding.

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. There's no mention of prerequisites (like authentication), when this operation is appropriate, or how it relates to sibling tools like 'list_mailboxes' or 'select_mailbox'.

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/Soundhannes/IMAP-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server