Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_messages

Lists emails from a specified Outlook folder with pagination, full-text keyword search, or OData filtering to find messages by sender, read status, or date.

Instructions

List Messages from a mail folder. Use folder 'inbox', 'drafts', 'sentitems', or 'deleteditems' (well-known names), or pass a folderId from list_mail_folders. Supports full-text search and OData filter — but NOT both at once.

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

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of messages to return (default: 50)
skipNoNumber of messages to skip (for pagination)
filterNoOData filter expression (e.g. 'isRead eq false'). Cannot be combined with search.
folderNoFolder name or ID to list from. Well-known names: 'inbox', 'drafts', 'sentitems', 'deleteditems'. Default: 'inbox'
searchNoFull-text keyword search (KQL). Cannot be combined with filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 behavioral burden. It discloses the mutual exclusivity of search and filter, which is genuinely behavioral, but says nothing about result ordering, permissions/scopes required, rate limits, or what message fields come back — significant gaps for a no-annotation list tool.

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?

Two tight sentences with zero filler; the folder-selection rule is front-loaded and the search/filter constraint closes it. Every clause carries operational information.

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?

With five all-optional, fully documented parameters and no output schema, the description covers routing, folder naming, and mode exclusivity adequately. It stops short of describing return shape or ordering, but that gap is modest given the schema already handles the parameters.

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 every parameter (top, skip, filter, folder, search) is already documented with its own description, including the search/filter conflict and default folder. The description repeats rather than extends that information, 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 Messages from a mail folder') plus the scope (folder-scoped listing). It gestures at the sibling relationship by pointing to list_mail_folders as the source of folderId, but does not explicitly contrast itself with get_message or the search-style siblings.

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 actionable context: which well-known folder names are valid, and the prerequisite of calling list_mail_folders to obtain a folderId. It also states the search-vs-filter exclusivity, though it does not explicitly say when to prefer this tool over fetching individual messages.

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