Skip to main content
Glama

manage-rules

Destructive

Create, list, update, reorder, or delete inbox rules with conditions, actions, and optional exceptions to automate email handling.

Instructions

Manage inbox rules. action=list (default) lists rules. action=create creates a new rule with conditions, actions, and optional exceptions. action=update modifies an existing rule. action=reorder changes rule execution priority. action=delete removes a rule.

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)
Behavior4/5

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

Annotations already set destructiveHint=true, and the description confirms by mentioning destructive operations (delete, reorder). It adds context that create/update accept conditions and exceptions, but does not detail authorization needs or irreversible consequences.

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 concise paragraph that front-loads the main verb. It could be improved with bullet formatting for actions, but every sentence adds value.

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?

Given 37 parameters and no output schema, the description covers actions but omits error handling, default values for many parameters, and return value details. It is adequate for basic use but lacks completeness for complex scenarios.

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 coverage is 100% with detailed parameter descriptions. The tool description adds minimal semantic value beyond the schema, only summarizing actions. Baseline 3 is appropriate.

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 it manages inbox rules, enumerates all five actions (list, create, update, reorder, delete), and distinguishes from sibling tools (no other rule tool exists).

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 implies usage through listing actions but does not explicitly state when not to use this tool or describe prerequisites. However, no alternative rule tool exists, so the guidance is adequate.

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