Skip to main content
Glama

graph_create_mail_folder

Creates a new Outlook mail folder at the top level or under a parent folder, and can target a shared mailbox when delegated permissions are available.

Instructions

Create a mail folder.

Args: display_name: Name of the new folder. parent_folder_id: Parent folder ID. Empty creates a top-level folder. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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

Input Schema

NameRequiredDescriptionDefault
mailboxNo
display_nameYes
parent_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states that targeting a shared mailbox requires delegated Mail.*.Shared permissions and explains default behavior for empty parent_folder_id and mailbox, but it does not describe what happens if the folder already exists, what the response contains, or other mutation side effects.

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?

The description is front-loaded with the core action and then uses a compact Args list for parameter details. It is appropriately sized for a simple three-parameter tool, though the permission sentence could arguably be integrated more tightly.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers parameter behavior and a key permission requirement well. It omits when-to-use guidance relative to siblings and does not explain return values or error/edge cases such as duplicate folder names, leaving some context gaps.

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?

Schema description coverage is 0%, so the description must compensate entirely. It documents all three parameters meaningfully: display_name names the new folder, parent_folder_id empty creates a top-level folder, and mailbox empty targets the user's own mailbox while shared mailboxes require delegated permissions.

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 a mail folder.' This clearly identifies the operation, but it does not explicitly distinguish it from the sibling 'graph_create_folder' or mention how it differs from other folder-related tools.

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

Usage Guidelines3/5

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

Usage conditions are implied through parameter descriptions, such as using parent_folder_id to create nested folders and mailbox to target shared mailboxes. However, there is no explicit guidance on when to use this tool versus alternatives like graph_create_folder or graph_list_mail_folders.

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