Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_get_categories

Lists all categories for an Outlook email account, helping you inspect available labels before organizing or filtering messages.

Instructions

List all categories for an email account (Outlook only)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>"
    },
    "name": "email_get_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'List' implies a read-only operation, but nothing states whether the call fails for non-Outlook accounts, whether an empty result is possible, or what a category record contains — all relevant for a list operation on an account-scoped resource.

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?

One short sentence with the resource, scope, and platform constraint front-loaded and no filler. Nothing could be removed without losing meaning.

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?

For a simple one-parameter list tool with no output schema, the definition is minimally viable, but it leaves the accountId format and the failure mode for non-Outlook accounts undocumented, which are the two things an agent most needs before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter accountId has 0% schema description coverage and is never mentioned in the description. The phrase 'for an email account' hints at account scoping but gives no guidance on the identifier's expected format or where to obtain it (e.g., via email_list_accounts).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('categories') scoped to 'an email account', plus the 'Outlook only' qualifier that separates it from label-oriented siblings like email_get_labels. It stops short of explicitly naming the alternative for non-Outlook accounts, but an agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '(Outlook only)' note implicitly tells the agent when this tool applies versus a Gmail-label equivalent, but it never states that condition outright or names the alternative to use otherwise. Usage is implied rather than prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.