Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_contact_folders

List your Outlook contact folders to find contact lists by name or ID. Retrieve folder IDs needed to browse contacts inside each folder with list_contacts.

Instructions

List the user's contact folders (contact lists) from Outlook, such as 'My ThailandPostMart - Dev'. To see contacts inside a folder, use list_contacts with the folderId.

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_contact_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of items to return (default: 50)
skipNoNumber of items to skip (for pagination)
folderIdNoIf provided, list contacts inside this folder instead of listing folders

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?

With no annotations, the description carries the full behavioral burden. "List" implies a read-only operation and the example adds concreteness, but nothing is said about pagination defaults, result ordering, or what a folder entry contains. The schema covers top/skip, so the main remaining gap is the return shape.

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 short sentences, front-loaded with what the tool does and followed by the sibling routing rule. The example folder name is useful context rather than filler. It could be slightly tighter, but nothing is wasted.

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 zero-required-parameter list tool this is close to sufficient: purpose and routing are covered. Gaps remain around return shape (no output schema) and the unresolved folderId behavior, which an agent would need in order to call it correctly in every case.

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 description coverage is 100%, so the baseline is 3. The description actually introduces tension with the schema: it directs folderId usage to list_contacts, while the schema says providing folderId here lists contacts inside the folder. It adds no clarifying semantics beyond the schema and leaves that overlap unresolved.

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?

The description names a specific verb and resource ("List the user's contact folders (contact lists) from Outlook") and gives a concrete example folder name, so an agent can distinguish it from list_contacts and list_mail_folders. It stops short of 5 because the schema's folderId parameter muddies the tool's scope, and the description does not reconcile that.

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?

It gives an explicit routing rule: "To see contacts inside a folder, use list_contacts with the folderId." That is clear when-to-use-the-sibling guidance. It does not mention list_mail_folders, though names alone cannot establish that tool's behavior, so the omission is minor.

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