Outlook MCP Server

Overview Schema Source Related Servers Discussions Admin

empty_folder

Permanently delete all messages in Outlook's Junk Email or Deleted Items folder, leaving subfolders untouched. Requires a matching message count to confirm; deletion cannot be undone.

Instructions

Permanently delete everything in Junk or Deleted Items, like Outlook's "Empty folder". Cannot be undone. Subfolders are left alone.

folder: junkemail or deleteditems. confirm_count: must equal the folder's current message count. Call without it first to get the count, and show it to the user. Deletes at most 1000 per call; if remaining is above zero, call again.

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": {
      "folder": "<folder>"
    },
    "name": "empty_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folder`	Yes
`confirm_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states the deletion is permanent and cannot be undone, subfolders are untouched, at most 1000 messages are deleted per call, and the caller should repeat while remaining is above zero. It also explains the confirm_count safety gate and user-visible count workflow.

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 front-loaded with the destructive scope and irreversible warning, then moves directly into parameter and pagination behavior. Every sentence adds operational value with no redundant wording.

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?

For a destructive tool with no annotations, no output schema, and zero schema descriptions, the definition is complete: it covers scope, irreversibility, subfolder exclusion, folder choices, confirmation requirements, pagination, and repeat-call behavior. The only minor omission is explicit permission requirements, but nothing essential for correct invocation is missing.

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. It defines folder values as junkemail or deleteditems and explains confirm_count as needing to equal the folder's current message count, including the important instruction to call first without it to obtain the count.

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 states a specific destructive action and scope: permanently delete everything in Junk or Deleted Items, like Outlook's Empty folder. It also distinguishes the behavior by noting subfolders are left alone.

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?

It clearly states the allowed folders and provides a required confirmation workflow, including calling without confirm_count first and showing the count to the user. It does not explicitly compare against alternatives such as permanently_delete_messages, so it falls short of full when-to-use guidance.

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