Skip to main content
Glama

Make a folder in a mailbox

create_folder

Makes a folder in a mailbox, at the top or under another folder, to file threads in. Every holder of the box sees it, in the webmail and in their mail client. A name holds no "/", "*" nor "%", is unique among its neighbours, and at the top is none of the six every mailbox has.

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

Input Schema

NameRequiredDescriptionDefault
boxYesThe address of the mailbox to look in, for example "simon@sonentreprise.com": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders.
nameYesThe name of the folder, 200 characters at most.
parent_idNoThe folder it goes under, by its id from list_folders. Left out, it goes at the top.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / box / description
      Previous value: -"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. A support queue is not a mailbox and has no folders."New value: +"The address of the mailbox to look in, for example \"simon@sonentreprise.com\": call list_sender_addresses to find it. One of its aliases names the same mailbox. A support queue is not a mailbox and has no folders."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioural burden and does disclose the key side effect: every holder of the mailbox sees the new folder in webmail and in their mail client. It also states validation rules that will cause failures. Permission requirements and what the call returns (for example, a folder id) are left unstated.

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?

Three dense sentences, each earning its place: purpose and scope first, then the side effect, then the constraint set. There is no filler or repetition, despite a slightly telegraphic grammar in the naming clause.

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 three-parameter mutation tool with no annotations and no output schema, the description covers purpose, visibility impact, and input constraints well. It stops short of saying how failures such as a duplicate name surface or what identifier comes back, but the essential calling information is present.

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%, so all three parameters are already documented, yet the description adds real meaning beyond the schema: character restrictions on the name, uniqueness among sibling folders, and the fact that certain names are reserved at the top level. Only the box parameter gets no extra detail in the description.

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?

"Makes a folder in a mailbox, at the top or under another folder" gives a concrete verb and resource, and the nesting scope is stated explicitly. It separates creating a folder from deleting or updating one only implicitly, with no sibling named, so it falls just short of a 5.

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?

The phrase "to file threads in" hints at the use case, and the naming constraints (no "/", "*", "%", unique among neighbours, not one of the six default top-level names) tell the agent what will be rejected. There is no explicit guidance on when to create a new folder instead of updating an existing one, and no prerequisites such as permissions are described.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources