Skip to main content
Glama

List messages

list_messages
Read-only

Retrieve messages from a specified Outlook folder, newest first, including sender, subject, preview, read/flag state and IDs; page results with offset/nextOffset.

Instructions

List messages in a folder, newest first, with sender, subject, preview, read/flag state and IDs. Page with offset/nextOffset. Times are UTC.

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
limitNoMessages to return (default 25)
orderNoSort order by received time (default "newest")
filterNoServer-side filter (default "all")
folderNoFolder (default inbox). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
offsetNoNumber of messages to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the read-only safety profile is covered. The description adds genuinely useful behavior beyond that: the newest-first ordering, offset/nextOffset paging model, and that timestamps are UTC. It does not mention default page size or any volume/rate considerations, so it stops short of rich behavioral context.

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?

Three short sentences, front-loaded with the core action and return payload, then paging, then the UTC caveat. Every sentence carries information, though "newest first" is partially redundant with the order parameter's default.

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?

There is no output schema, so the description usefully compensates by naming the returned fields and the nextOffset paging token. For a five-parameter read tool with full schema coverage and clear annotations, nothing essential to correct invocation is missing.

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 all five parameters (limit, order, filter, folder, offset) are already fully documented in the schema, including enums and defaults. The description only echoes the ordering default and paging concept, adding no syntax or format detail beyond the schema; 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?

Clear verb+resource ("List messages in a folder") plus a precise enumeration of returned fields (sender, subject, preview, read/flag state, IDs) and default ordering. It does not name a sibling like search_messages or get_message to differentiate scope, which keeps it short of a 5.

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 folder scoping and default sort imply browsing usage, but there is no explicit statement of when to use this instead of search_messages or get_message, nor any exclusions. Usage is inferable but not stated.

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