Skip to main content
Glama

delete_email

Remove a specified Outlook email by message ID through Microsoft Graph, enabling automated cleanup of unwanted inbox messages.

Instructions

Delete an email

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_id": "<message_id>"
    },
    "name": "delete_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe ID of the email message to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden for a destructive operation, yet it discloses nothing about permanence, recoverability, permission requirements, or side effects. The sentence essentially restates the tool name and adds no behavioral context.

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?

The description is a single short sentence with zero wasted words and is trivially front-loaded. Its brevity is efficient, though it reflects under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive one-parameter mutation with no annotations and no output schema, an agent needs to know whether the deletion is reversible and what it returns. The description supplies none of this, leaving the definition inadequate relative to the operation's risk.

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% and the single parameter (message_id) is fully documented in the schema, so the description does not need to explain it. Baseline 3 applies since the description adds no meaning beyond the structured field.

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 states a specific verb and resource ('Delete an email') and is readily distinguishable from the read/list/search/mark_as_read siblings. It stops short of clarifying whether deletion is permanent or moves the message to trash, which leaves a meaningful ambiguity about the operation itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as marking as read, and no mention of prerequisites or confirmation. The only implied usage is 'when you want an email gone,' which the agent could infer from the name alone.

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