Skip to main content
Glama

apply-category

Categorize email messages by setting, adding, or removing master categories. Supports single or batch messages for efficient organization.

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?

Describes batch operation via Graph $batch, matching by display name, and returns per-message confirmation. Annotations indicate non-readonly, consistent with description. No contradictions.

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?

Single paragraph is well-structured: main purpose first, then action details, inputs, and prerequisites. No unnecessary words, but could be slightly more concise.

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, description explains return type (per-message confirmation). Covers all parameters and prerequisites. Adequately complete for operation 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%, but description adds context: explains exclusive use of messageId/messageIds, action defaults and effects, and requirement that categories exist.

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 or untags email messages with master categories, specifying three actions (set, add, remove). It distinguishes from manage-category by noting categories are created there.

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?

Explicitly notes that categories must exist (create via manage-category first) and explains each action's behavior. Could specify when not to use but provides sufficient context.

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