Mail-MCP

Overview Schema Source Related Servers Discussions Admin

Create folder

mail_create_folder

Idempotent

Create a new Outlook folder at the root or within a specified parent folder. If the folder already exists, it returns the existing folder without error.

Instructions

Create an Outlook folder (at the root or under a parent). Idempotent: if a folder with the same name already exists it is returned without error. Example: { name: "Newsletters" } or { name: "2025", parent: "Invoices" }.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the folder to create
`parent`	No	Parent folder (name, path or id). Root if omitted.

Output Schema

Name	Required	Description	Default
`folder`	Yes
`created`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, and the description restates this with 'if a folder with the same name already exists it is returned without error.' While the description adds a slight detail ('without error'), it does not introduce new behavioral information beyond the annotation. Other behaviors (e.g., auth requirements, error on missing parent) are not disclosed.

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 three sentences with zero fluff: action, idempotency, and examples. It front-loads the core purpose and uses a compact, informative format that an agent can parse quickly.

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?

Given the tool's simplicity (2 params, both documented), the presence of an output schema, and annotations covering idempotency and safety, the description covers everything an agent needs to invoke it correctly. No critical information is missing.

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

Parameters4/5

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

Schema coverage is 100% and both parameters are described. The description adds concrete usage examples ('Newsletters', '2025' with parent 'Invoices') that clarify how to structure calls, which goes beyond the schema's terse descriptions and helps an agent compose correct inputs.

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?

The description states a specific verb ('Create'), a resource ('Outlook folder'), and scope ('at the root or under a parent'). It clearly differentiates from siblings like mail_list_folders and mail_move by its action, leaving no ambiguity about what the tool does.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (creating folders) and includes practical examples. It does not explicitly name alternatives or exclusions, but the purpose is so distinct among siblings that an agent can infer usage without confusion.

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

Deploy Server