Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti

outlook_delete_folder

Delete a user-created mail folder by its ID while preventing deletion of well-known folders like Inbox and Sent Items.

Instructions

Delete a user-created mail folder by ID; refuses well-known folders (inbox, sentitems).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYes
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 burden. It discloses a behavioral trait: the tool refuses well-known folders. However, it does not mention whether deletion is permanent, if confirmation is needed, or any error handling behavior.

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?

The description is a single concise sentence that front-loads the action and constraint with no extraneous words.

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 simple deletion tool with one parameter and no output schema, the description covers the purpose and a key constraint. However, it lacks details about the irreversibility of deletion and potential errors (e.g., when providing a non-existent folder ID).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not add any information about the folder_id parameter beyond what the schema provides (type string, required). With 0% schema description coverage, the description should compensate but fails to do so.

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 the action (delete) and the resource (user-created mail folder by ID) and adds a key constraint (refuses well-known folders), making it specific and distinguishing from sibling tools like outlook_delete_message.

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 explicitly states that well-known folders are refused, implying it's for user-created folders only. However, it does not provide explicit guidance on when to use this tool versus alternatives like outlook_delete_message or outlook_delete_event.

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/mpalermiti/outlook-mcp'

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