Skip to main content
Glama

graph_create_message_rule

Create an Exchange inbox rule to automatically process incoming mail. Define conditions and actions such as moving matching messages to a folder, marking them as read, or deleting them.

Instructions

Create an inbox rule that Exchange runs on incoming mail.

At least one condition and at least one action are required; only the parts you supply are sent to Graph.

Args: display_name: Name of the rule. sequence: Order in which the rule runs, lowest first (default 1). from_addresses: Sender addresses the rule matches. subject_contains: Strings the subject must contain. body_contains: Strings the body must contain. move_to_folder: Destination folder ID for matching messages. mark_as_read: Whether matching messages are marked read (default false). delete_message: Whether matching messages move to Deleted Items (default false). is_enabled: Whether the rule is active (default true). stop_processing: Whether later rules are skipped once this rule matches (default false). 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": {
      "display_name": "<display_name>"
    },
    "name": "graph_create_message_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
sequenceNo
is_enabledNo
display_nameYes
mark_as_readNo
body_containsNo
delete_messageNo
from_addressesNo
move_to_folderNo
stop_processingNo
subject_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses defaults, that only supplied fields are sent, and that shared mailbox targeting requires delegated Mail.*.Shared permissions, but it does not describe the return result, general write permissions, or error/duplicate-rule behavior.

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?

The description is front-loaded with purpose and the key condition/action constraint, followed by a clean parameter list. Every sentence and parameter note adds useful information without repetition.

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 an 11-parameter mutation tool with no output schema and no annotations, it is substantially complete: purpose, constraints, defaults, all parameters, and a shared-mailbox permission caveat are covered. It stops short of describing success/return behavior or broader permission requirements.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description must compensate. It documents every parameter, including default values, match semantics for conditions, destination folder behavior, and the mailbox permission requirement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: "Create an inbox rule" that Exchange runs on incoming mail. It is clearly a creation tool and is distinguishable from sibling list/delete message-rule tools without opening the schema.

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

Usage Guidelines4/5

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

It gives meaningful usage context: at least one condition and one action are required, and only supplied parts are sent to Graph. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of the top score.

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