Skip to main content
Glama

manage-rules

Destructive

Manage Outlook inbox rules with actions to list, create, update, reorder, or delete rules based on conditions like sender, subject, attachments, and more.

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

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds context: it notes the destructive nature, the use of dryRun for preview, that rules run server-side, and session rate limits. No contradiction with annotations.

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, well-organized paragraph. It front-loads the core purpose and then systematically covers each action. It is appropriately detailed for 37 parameters, though slightly verbose.

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?

The description explains return values for 'list' action (id/name/sequence) and dryRun preview, but does not describe return values for create/update/delete/reorder. It mentions session rate limits and recipient allowlist. Missing output schema partially offset by param descriptions.

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 100%, so baseline is 3. The description adds value by grouping parameters by action, explaining the logic for containsSubject/bodyContains (OR logic), and clarifying that action defaults to 'list'. It also notes the 12 supported condition params and 9 action params.

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 elaborates on actions. It distinguishes from client-side rules by noting they run on Exchange server regardless of client. This specificity differentiates it from sibling tools like manage-category.

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 guidance for each action, including when to use includeDetails, dryRun, and reorder. It also states that permanentDelete is intentionally omitted and should be done via Outlook UI. However, it does not directly compare to sibling tools for when to use this tool over others.

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-assistant'

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