Skip to main content
Glama
Sign In
mailpouch

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Folder

create_folder

Create a new IMAP mailbox as a folder or label by specifying an unused path. Use Folders/Name or Labels/Name to add a mailbox for organizing email.

Instructions

Create one new IMAP mailbox. Use Folders/Name for a custom folder or Labels/Name for a label; the path must be unused across both namespaces. Use rename_folder to change an existing mailbox. Returns success after Proton Bridge accepts the create; create labels before adding them with move_to_label.

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": {
      "folderName": "<folderName>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
folderNameYesFolder path to create (e.g. Folders/Archive, Labels/Work)

Output Schema

NameRequiredDescriptionDefault
reasonNo
successYes
messageIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only show readOnlyHint=false, destructiveHint=false, idempotentHint=false. Description adds that the path must be unique across namespaces and that success is returned after Bridge acceptance, providing useful behavioral context beyond annotations.

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?

Two sentences, front-loaded with the core action, no redundant words. Each sentence adds necessary information.

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

Completeness4/5

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

With full schema coverage and annotations, description covers creation, naming, return behavior, and related operations. Could mention error conditions like duplicate path, but overall sufficient.

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 already fully describes both parameters (100% coverage). Description adds format examples (e.g., Folders/Archive) and uniqueness requirement, which adds slight value but does not substantially exceed schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Clearly states 'Create one new IMAP mailbox' and distinguishes from rename_folder by mentioning it as an alternative for changing existing mailboxes.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says use Folders/Name or Labels/Name, name must be unused, and advises creating labels before adding with move_to_label. Also references rename_folder as alternative for modifications.

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

Deploy Server

Other Tools