Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

delete_message

Moves a specified Outlook message or draft to the Deleted Items folder so it can be recovered later instead of being permanently erased.

Instructions

Delete a Message or Draft by moving it to the Deleted Items folder. The message is NOT permanently erased — it can be recovered from Deleted Items.

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": {
      "messageId": "<messageId>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesThe Message ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden, and it does the most important part: it explicitly discloses that the operation is non-destructive ('NOT permanently erased') and that the item is recoverable from Deleted Items. It omits permission requirements and what the response contains, which keeps it short of a 5.

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?

Two short sentences, front-loaded with the action and immediately followed by the behavioral caveat that matters most to an agent deciding whether to call it. No filler.

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 single-parameter tool with no annotations and no output schema, the definition covers the key risk (reversibility) but leaves the return value and any permission constraints unstated. Adequate and close to complete for this complexity level.

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 coverage is 100% and the single messageId parameter is fully documented in the schema, so the description adds no parameter-level meaning beyond it. One nuance — that the ID may refer to either a message or a draft — is implied but not spelled out for the parameter itself.

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 uses a specific verb and resource ('Delete a Message or Draft') and clarifies the mechanism ('moving it to the Deleted Items folder'). It does not name or distinguish itself from any sibling, but the purpose is unambiguous on its own.

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 soft-delete mechanism implies when this tool applies versus a hard delete, but there is no explicit when-to-use statement, no prerequisites, and no reference to related operations. Usage is inferable rather than stated.

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