mcp-proton-mail

Overview Schema Source Related Servers Discussions Admin

Preview creating a folder

preview_create_folder

Read-only

Preview creating a new mail folder under Folders/ and get a single-use approval token without creating anything. Confirm the folder name first, then approve to create it.

Instructions

Preview creating one new mail folder under Folders/ and return a single-use approval token; creates nothing.

Use it when the user asks for a new folder: show the name, wait for explicit approval, then call create_folder with the token. To move mail into a folder that may not exist yet, use preview_action(action="move_to_folder") with create_folder_if_missing=true in params instead, which binds creating it to the move.

name is the exact full path, such as Folders/Receipts or Folders/Work/Clients. An existing folder needs no token: the result says exists=true and there is nothing to approve. The token works once, until expires_at.

Returns name, exists, token, expires_at and action_hash. Refuses a name outside Folders/, an empty, "." or ".." part, quotes, backslashes, * or %, or over 500 characters.

Input Schema

Name	Required	Description	Default
`name`	Yes	The exact new folder name, under Folders/.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

This is consistent with readOnlyHint=true ("creates nothing") and adds a lot beyond the annotations. It covers single-use tokens, expiry via expires_at, and the exists=true no-op case for existing folders. It also lists the validation refusals: paths outside Folders/, empty, "." or ".." parts, quotes, backslashes, * or %, and names over 500 characters.

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?

It is well organized into purpose, usage, parameter and returns/refusals sections, with the purpose front-loaded. Listing the return fields is slightly redundant given the output schema, but it is brief.

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

Completeness5/5

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

For a preview/approval tool, it covers the full lifecycle: the token flow, expiry, the existing-folder case, validation errors and the alternative path. Nothing an agent needs to use it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only says "exact new folder name, under Folders/". The description adds that this is the full path, gives nested examples (Folders/Work/Clients), and spells out the exact character and length constraints.

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?

It states a specific action: preview creating one mail folder under Folders/ and return a single-use approval token, while creating nothing. It sets this apart from create_folder, which consumes the token, and from preview_action's move_to_folder path.

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?

It gives the workflow explicitly: show the name, wait for explicit approval, then call create_folder with the token. It also names when to use an alternative instead: preview_action with action="move_to_folder" and create_folder_if_missing=true, for moves into a folder that may not exist.

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