Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_mail_folders

Retrieve all mail folders, including custom ones, and get folder IDs required to list messages in non-standard Outlook folders.

Instructions

List all mail folders in the authenticated user's mailbox, including custom folders. Returns folder IDs needed for list_messages with non-standard folders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_mail_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of folders to return (default: 50)
skipNoNumber of folders to skip (for pagination)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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, and the mailbox scope is useful context, but the description says nothing about pagination behavior, result ordering, or whether inaccessible folders are silently omitted.

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?

Two sentences, front-loaded with the scope and ending with the downstream use. Both sentences carry information; there is no padding or repetition of the name.

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?

A simple two-parameter read tool, but with no annotations and no output schema the description has to do more than state purpose. It hints at return content (folder IDs) yet omits the response shape, pagination expectations, and whether the list is complete or truncated.

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 top and skip already documented including defaults and pagination intent. The description adds no meaning beyond the schema for those parameters, so the baseline 3 applies.

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 and resource ('List all mail folders in the authenticated user's mailbox, including custom folders'), which clearly separates it from the contact-folder sibling. It stops short of naming any alternative tool, so sibling differentiation is implied by the resource rather than stated.

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?

Gives a concrete reason to call it: obtaining folder IDs that list_messages needs for non-standard folders. That's a usable trigger, but there is no when-not-to-use guidance or mention of what to do for standard folders.

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