Skip to main content
Glama

graph_delete_mail

Delete Outlook messages by moving them to Deleted Items and reporting per-message outcomes; process 1-50 message IDs per call in your or a shared mailbox.

Instructions

Delete messages. They are moved to Deleted Items, not erased.

Processes each message in order and reports per-message outcomes.

Args: message_ids: Message IDs to delete (1-50 per call). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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": {
      "message_ids": "<message_ids>"
    },
    "name": "graph_delete_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
message_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that deletion is soft (items go to Deleted Items, not erased), that processing is sequential with per-message outcome reporting, and that shared-mailbox use requires delegated Mail.*.Shared permissions. It omits throttling/rate-limit behavior and what happens on partial failure, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded: the effect (soft delete), then processing behavior, then argument docs. The Args block is easy to scan, with only minor redundancy in restating the 1-50 batch cap already encoded in the schema.

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 batch mutation with no annotations and no output schema, the definition covers the essential unknowns: reversibility, batching, ordering, per-item results, and shared-mailbox authorization. The absence of a described return shape is acceptable since outcomes are summarized qualitatively.

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

Parameters4/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 and largely does: mailbox is explained as an address or user ID with empty meaning 'your own mailbox' plus its permission requirement, and message_ids is tied to the 1-50 batch bound. The 1-50 detail duplicates the schema's minItems/maxItems, so the added value is mostly on mailbox.

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 gives a specific verb and resource — "Delete messages" — and immediately clarifies the deletion semantics (moved to Deleted Items). It does not explicitly distinguish itself from message-oriented siblings such as graph_delete_channel_message or graph_delete_chat_message, though the mailbox parameter and 'Mail.*.Shared' permission hint point to Outlook mail.

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 definition establishes context (soft delete, batch size, shared-mailbox targeting) but never says when to choose this over alternatives like graph_move_mail or graph_delete_message_rule. Usage is implied rather than stated, leaving routing decisions to the agent's inference.

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

Deploy Server

Other Tools