Skip to main content
Glama

Create folder

create_folder

Create a new mail folder in Microsoft 365, optionally nested inside an existing folder via parent name, path, or folder ID. Organize Outlook mail by building the folder structure you need.

Instructions

Create a mail folder, optionally inside another 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": {
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew folder name
parentNoParent folder (default: top level of the mailbox). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered structurally. The description adds only that the new folder may be nested, and says nothing about behavior on duplicate names, whether a missing parent errors out, or required permissions. Some value, but not rich.

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?

One short sentence with zero filler, and the primary action is front-loaded before the optional nesting detail. Nothing could be trimmed without losing 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?

For a simple two-parameter creation tool with full schema coverage and annotations present, the description covers the essentials. The only meaningful gap is the absence of duplicate-name or failure behavior, which an agent might want before invoking a write operation.

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%, with the 'parent' parameter already documenting well-known names, display paths, and folder IDs. The description adds nothing beyond that, so the baseline of 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 states a specific verb and resource (create + mail folder) and adds the nesting scope, so an agent knows exactly what is produced. It doesn't distinguish itself from sibling operations like rename_folder or move_folder, but the create action is unambiguous.

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 explicit guidance on when to use this versus alternatives such as move_folder (relocating an existing folder) or rename_folder, nor any prerequisite notes. At best the phrase 'optionally inside another folder' implies how nesting works, but no when/when-not conditions are given.

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