Skip to main content
Glama

Delete messages

delete_messages
Destructive

Delete one or more Outlook messages by ID, moving them to Deleted Items by default or permanently removing them when requested; permanent deletion cannot be undone.

Instructions

Delete messages. By default they are moved to Deleted Items (recoverable); permanent deletion cannot be undone.

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": {
      "ids": "<ids>"
    },
    "name": "delete_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
permanentNoPermanently delete (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the crucial nuance that the default path is recoverable and only permanent deletion is irreversible. That prevents an agent from over- or under-estimating the risk of the call, which is exactly the kind of context annotations cannot express.

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 with no filler, and the risk-relevant clause about irreversibility is placed where an agent will read it before deciding on the permanent flag.

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 two-parameter destructive tool with no output schema, the description covers the essential risk profile. It stops short of noting what happens on invalid IDs, mixed batches, or the 500-item batch limit, but those are largely carried by the schema.

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 100%, with the permanent flag already documented as "Permanently delete (default false)" and the ids array pointing to list_messages/search_messages/get_message as sources. The description reinforces the default behavior but adds no new detail about the id format, the 500-item cap, or partial-failure semantics.

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 specific verb and resource ("Delete messages") and immediately clarifies the scope of deletion. It does not name a sibling such as move_messages to contrast against, but the "moved to Deleted Items" wording implicitly separates it from a general move operation.

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?

It explains the default outcome and the consequence of the permanent flag, which is the main usage decision an agent faces. However, it gives no explicit guidance on when an agent should choose permanent=true versus a soft delete, nor does it point to move_messages or delete_folder for other destinations.

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