Skip to main content
Glama

manage-rules

Destructive

Manage Outlook inbox rules: list, create, update, reorder, or delete server-side rules. Preview changes with dry-run before applying.

Instructions

Server-side inbox rule CRUD (destructive: covers delete; supports dryRun on create/update for preview). Rules run on the Exchange server regardless of which client is open. action=list (default) returns rules with id/name/sequence — pass includeDetails: true to expand conditions/actions/exceptions. action=create builds a new rule from condition params (12 supported: fromAddresses, containsSubject, bodyContains, hasAttachments, importance, sentTo, sensitivity, etc.), action params (9 supported: moveToFolder, forwardTo, redirectTo, assignCategories, markAsRead, delete, etc.), and optional except* exceptions. action=update patches the named fields by ruleId. action=reorder changes execution priority via sequence (lower = earlier). action=delete removes a rule. Recipient allowlist applies to forwardTo/redirectTo. permanentDelete action is intentionally omitted (too dangerous for AI use — use the Outlook UI). Subject to session rate limits (OUTLOOK_MAX_MANAGE_RULES_PER_SESSION).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRule name (action=create required, action=update to rename)
actionNoAction to perform (default: list)
dryRunNoPreview rule without creating/updating (action=create, action=update)
ruleIdNoID of existing rule (action=update/delete)
ruleNameNoName of existing rule (action=update/reorder/delete)
sentCcMeNoMatch emails where I am in CC (action=create/update)
sentToMeNoMatch emails sent to me (action=create/update)
sequenceNoExecution order, lower = higher priority (action=create default: auto, action=reorder required)
forwardToNoComma-separated emails to forward matching messages to (action=create/update)
isEnabledNoEnable/disable rule (action=create default: true, action=update)
importanceNoMatch emails with this importance (action=create/update)
markAsReadNoMark matching emails as read (action=create/update)
redirectToNoComma-separated emails to redirect matching messages to (action=create/update)
displayNameNoAlias for `name` (matches Graph's own `displayName` field).
sensitivityNoMatch emails with this sensitivity (action=create/update)
bodyContainsNoComma-separated body text keywords (OR logic) (action=create/update)
copyToFolderNoFolder name to copy matching emails to (action=create/update)
moveToFolderNoFolder name to move matching emails to (action=create/update)
sentOnlyToMeNoMatch emails where I am the only recipient (action=create/update)
deleteMessageNoMove matching emails to Deleted Items (action=create/update)
fromAddressesNoComma-separated sender emails to match (action=create/update)
hasAttachmentsNoMatch emails with attachments (action=create/update)
includeDetailsNoInclude detailed conditions, actions, and exceptions (action=list)
markImportanceNoSet importance on matching emails (action=create/update)
senderContainsNoComma-separated partial sender matches (action=create/update)
containsSubjectNoComma-separated subject keywords (OR logic). e.g. "invoice, receipt, payment" (action=create/update)
sentToAddressesNoComma-separated recipient emails to match (action=create/update)
assignCategoriesNoComma-separated Outlook categories to assign (action=create/update)
isAutomaticReplyNoMatch automatic reply emails (action=create/update)
recipientContainsNoComma-separated partial recipient matches (action=create/update)
exceptBodyContainsNoComma-separated body keywords to exclude (action=create/update)
exceptFromAddressesNoComma-separated sender emails to exclude (action=create/update)
stopProcessingRulesNoStop evaluating subsequent rules (action=create/update)
exceptHasAttachmentsNoExclude emails with attachments (action=create/update)
exceptSenderContainsNoComma-separated partial sender matches to exclude (action=create/update)
bodyOrSubjectContainsNoComma-separated keywords matching body OR subject (OR logic) (action=create/update)
exceptSubjectContainsNoComma-separated subject keywords to exclude (action=create/update)
Behavior5/5

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

The description discloses that the tool is destructive (covers delete) and that 'permanentDelete' is intentionally omitted for safety. It explains that rules run server-side regardless of client, supports dryRun for preview, and is subject to session rate limits. This adds significant value beyond the annotations (destructiveHint=true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single dense paragraph covering many aspects. It is front-loaded with the main purpose but could benefit from bullet points or clearer separation of actions. However, given the tool's complexity with 37 parameters, it remains reasonably efficient without redundant sentences.

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

Completeness5/5

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

For a tool with 37 parameters, no output schema, and only basic annotations, the description covers all necessary context: all actions are explained, parameters are grouped logically, safe preview via dryRun is highlighted, dangerous operations are excluded, and rate limits are noted. It is fully adequate for an agent to select and invoke the tool correctly.

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?

While the input schema already describes each parameter (100% coverage), the description groups condition parameters (12 supported), action parameters (9 supported), and exception parameters, and explains the logical OR for keyword searches. It clarifies the relationship between 'name' and 'displayName' and provides examples (e.g., 'invoice, receipt'). This adds meaningful semantic grouping.

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 clearly states 'Server-side inbox rule CRUD' and enumerates each action (list, create, update, reorder, delete), specifying that it covers destructive operations. It distinguishes itself from sibling tools like 'manage-focused-inbox' and 'apply-category' by focusing on inbox rules, and mentions intentional omission of permanentDelete as too dangerous.

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?

The description provides explicit context for each action: default action is list, dryRun for preview, reorder changes sequence, etc. It also warns about rate limits and the omission of permanentDelete. However, it does not explicitly compare to sibling tools or advise when to use this tool over others like 'manage-focused-inbox'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/littlebearapps/outlook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server