Skip to main content
Glama

graph_delete_message_rule

Delete an Outlook inbox rule by rule ID, optionally targeting a shared mailbox. Use it to remove automated sorting or forwarding rules that are no longer needed.

Instructions

Delete an inbox rule.

Args: rule_id: The rule ID (from graph_list_message_rules). 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": {
      "rule_id": "<rule_id>"
    },
    "name": "graph_delete_message_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
rule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden for a destructive operation. It usefully adds that an empty mailbox targets your own mailbox and that shared mailboxes require delegated Mail.*.Shared permissions, but it says nothing about whether the delete is permanent/irreversible or what happens on an invalid rule_id.

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?

One-line purpose followed by a two-arg Args block, with no filler. The purpose is front-loaded ahead of the parameter notes and nothing redundant is repeated from the schema.

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

Completeness3/5

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

For a simple two-parameter delete with no output schema and no annotations, most of what an agent needs is present. What's missing is destructive-operation context: irreversibility, confirmation expectations, and error behavior on a bad rule_id.

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 coverage is 0%, so the description has to compensate, and it largely does: rule_id is sourced to graph_list_message_rules, and mailbox is explained as an address or user ID with an empty default meaning your own mailbox, plus the permission prerequisite. The only gap is the expected ID format 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?

States a specific verb and resource ("Delete an inbox rule"), which is immediately distinguishable from siblings like graph_list_message_rules and graph_create_message_rule by the verb alone. It doesn't explicitly name an alternative or scope nuance, but the purpose is unambiguous.

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 rule_id arg points back to graph_list_message_rules, giving an implicit prerequisite workflow for obtaining a valid ID. However, there is no guidance on when to choose this over other delete siblings, and no caution about when not to delete.

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