Skip to main content
Glama

manage-focused-inbox

List, set, or delete sender overrides to route emails to Focused or Other folders, overriding the automatic classifier.

Instructions

Manage Focused Inbox sender overrides — explicit rules that force messages from a given sender into Focused or Other regardless of the ML classifier. action=list (default) returns existing overrides with id/sender/classifyAs. action=set creates or updates an override for emailAddress (optional name), routing future mail to focused (default) or other. action=delete removes the override for emailAddress. Note: this only works on accounts that have Focused Inbox enabled — personal Outlook.com accounts without it return an empty list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction to perform (default: list)
outputVerbosityNoOutput detail level (action=list, default: standard)
emailAddressNoSender email address (action=set/delete, required)
nameNoSender display name (action=set)
classifyAsNoWhere to put emails from this sender (action=set, default: focused)
Behavior5/5

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

The description transparently discloses behavioral traits: actions (list is safe, set creates/updates, delete removes), preconditions (Focused Inbox must be enabled), and expected results (list returns override details, set/delete affect future mail). This adds context beyond annotations (readOnlyHint=false, destructiveHint=false).

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 concise (4 sentences), front-loaded with the tool's purpose, and efficiently explains actions without redundancy. Every sentence serves a purpose.

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 no output schema, the description explains return values for list (id/sender/classifyAs) and notes the empty list case for non-enabled accounts. It covers setup, actions, defaults, and limitations, making it fully self-contained.

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?

The input schema already describes all 5 parameters with 100% coverage. The description reinforces defaults (action=list, classifyAs=focused) and dependencies (emailAddress required for set/delete) but adds limited new meaning—hence baseline 3.

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 the tool manages Focused Inbox sender overrides, specifying three distinct actions (list, set, delete) with clear behavior for each. It distinguishes from sibling tools by focusing on a specific feature (Focused Inbox), not general mailbox rules.

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 when to use the tool (accounts with Focused Inbox enabled) and notes that setting requires an email address. However, it does not explicitly contrast with siblings like 'manage-rules' or 'mailbox-settings', leaving the agent to infer usage boundaries.

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