Skip to main content
Glama

Email: Create folder

email_create_folder

Create a mailbox folder/label. parent_id, when supplied, must be an exact existing folder ID resolved from email_list_folders; it is not a parent folder display name.

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": "email_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
parent_idNoExact existing parent folder ID. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the agent knows this is a non-idempotent write. The description adds the constraint that parent_id must be an exact existing ID rather than a display name, but it says nothing about duplicate-name behavior, error handling, or required permissions. Given the annotations carry the safety information, a 3 is appropriate.

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?

Two sentences, front-loaded with the purpose and followed by the single most error-prone constraint. Nothing is padded. The second sentence largely repeats the parent_id schema description, which is a minor redundancy rather than a structural flaw.

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 three-parameter mutation tool with no output schema, the definition omits what the call returns (folder object? ID?), how duplicate names are handled given idempotentHint=false, and how it relates to email_update_folder. It is minimally adequate but leaves the agent to infer outcome behavior.

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 description coverage is 67% and both parent_id and account_id already carry detailed schema descriptions, including the same 'exact ID, never a display name' warning. The description reinforces the parent_id rule but adds no new syntax, format, or fallback behavior beyond the schema. The unlabeled 'name' parameter is the only true gap, and it is self-evident.

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 opens with a concrete verb+resource: 'Create a mailbox folder/label.' That is unambiguous and matches the title, and the sibling set makes the intent distinguishable (email_update_folder, email_delete_folder). It stops short of explicitly differentiating the create operation from those siblings, so a 4 rather than 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?

There is one embedded workflow rule — parent_id must be 'resolved from email_list_folders' — which tells the agent a prerequisite step and names the sibling that satisfies it. However, there is no guidance on when to create a top-level folder versus a nested one, what to do if a folder with the same name already exists, or which sibling to prefer if the user's intent is ambiguous.

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.