Skip to main content
Glama

imap_create_mailbox

Create a new IMAP mailbox or folder, such as Archive/2024, in a specified account to organize email. Provide the mailbox name; the account defaults to the default account.

Instructions

Create a new mailbox/folder

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mailbox_name": "<mailbox_name>"
    },
    "name": "imap_create_mailbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default
mailbox_nameYesName of the mailbox to create (e.g., `Archive/2024`, `Projects/Active`)

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already cover the safety profile (not read-only, not destructive, open-world), so the description's job is to add context, and it adds none. Most notably, idempotentHint=false means creating an existing mailbox presumably errors, but the description never states what happens on a name conflict, whether intermediate path segments are auto-created, or whether changes are immediate.

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

Conciseness4/5

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

A single short clause, front-loaded with the verb and resource, with no filler or redundancy. Its brevity is efficient, though it borders on under-specification rather than optimal concision.

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, the definition is nearly a restatement of the tool name, leaving conflict behavior, hierarchy semantics, and account targeting to the schema and annotations. An output schema exists so return values need not be described, but the missing behavioral context for a non-idempotent create is a real gap.

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 coverage is 100% and the schema already explains both parameters, including a path-style mailbox_name example and the account_id default. The description contributes nothing about naming rules, path delimiters, or multi-account behavior, so the baseline 3 applies.

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 gives a clear verb+resource ("Create a new mailbox/folder") and clarifies that a mailbox is a folder, which the tool name alone does not. It does not differentiate from siblings such as imap_rename_mailbox or imap_delete_mailbox, nor does it indicate where in the hierarchy the new folder lands.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., rename vs. create, or which account/folder parent to target), and no prerequisites given. The agent must infer that this is the tool to use whenever a new folder is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.