Skip to main content
Glama

Delete Email Folder

emailfolders_delete
Destructive

Delete a mail folder permanently, including all emails and subfolders, with user confirmation required to prevent accidental loss.

Instructions

🔴 Delete a mail folder permanently (always require user confirmation)

WARNING: This action permanently deletes the folder and all its contents (emails and subfolders) and cannot be undone.

Args: folder_id: The folder ID to delete account_id: Microsoft account ID confirm: Must be True to confirm deletion (prevents accidents)

Returns: Status confirmation

Raises: ValueError: If folder_id is invalid or confirm is False

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes
account_idYes
confirmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds critical behavior: 'WARNING: This action permanently deletes the folder and all its contents (emails and subfolders) and cannot be undone.' It also clarifies the confirm parameter requirement, which is not in annotations.

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 structured with a clear warning, parameter list, and returns/raises sections. Each sentence serves a purpose, though the multiple warnings could be slightly condensed without losing clarity.

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 destructive nature (destructiveHint=true) and the output schema presence, the description covers all necessary aspects: purpose, usage warnings, parameter semantics, return values, and error conditions. It leaves no critical gaps for an AI agent.

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?

Despite 0% schema description coverage, the description fully explains each parameter: folder_id (the folder ID), account_id (Microsoft account ID), and confirm (must be True to confirm). It also documents the ValueError for invalid folder_id or false confirm, adding semantic value beyond the schema.

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 clearly states 'Delete a mail folder permanently' and includes a warning about permanent deletion. It distinguishes itself from sibling tools like emailfolders_create, emailfolders_rename, and others by specifying the destructive nature.

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 notes that the action 'always require[s] user confirmation' and warns about permanent deletion. It implicitly guides usage by emphasizing the need for caution, though it does not explicitly list alternatives or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robin-collins/m365-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server