Skip to main content
Glama

apply-category

Set, add, or remove category labels on Outlook email messages. Use message ID or batch IDs to replace, append, or remove categories by display name.

Instructions

Tag or untag email messages with master categories (those created via manage-category). action=set (default) replaces the message's category set with the supplied categories array. action=add appends categories to whatever's already on the message. action=remove removes only the named categories, leaving the rest. Accepts either messageId (single) or messageIds (batch via Graph $batch). categories are matched by display name — names must already exist in the master list (create via manage-category first). Returns per-message confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdNoSingle message ID to categorise
messageIdsNoArray of message IDs to categorise (batch operation)
categoriesYesCategory display names to apply/remove (required)
actionNoset (replace all), add (append), remove (remove specific). Default: set
Behavior4/5

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and potentially modifies data (destructiveHint=false). The description adds specific behavioral details: action meanings, batch behavior via $batch, and per-message confirmation return. No contradictions 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.

Conciseness5/5

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

The description is concise (4 sentences) and front-loaded with the purpose. Each sentence adds necessary detail (actions, input options, precondition, return value) without redundancy.

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?

Given no output schema, the description mentions per-message confirmation. It covers all parameters, action behaviors, batch capability, and prerequisite. The sibling manage-category is referenced. No gaps identified for this tool's complexity.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that categories are matched by display name, that they must exist in master list, that messageIds triggers batch via Graph $batch, and clarifies the action enum effects beyond the schema's definition.

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 tags/untags email messages with master categories, distinguishes from sibling manage-category (which creates categories), and details the three actions (set, add, remove).

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 explains when to use each action (set replaces, add appends, remove removes) and notes that categories must already exist in the master list via manage-category, providing implicit guidance on prerequisites. However, it doesn't explicitly state when not to use this tool in favor of alternatives, though the sibling context makes this clear.

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