Skip to main content
Glama
littlebearapps

Outlook Assistant

by littlebearapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Shared Mailbox

access-shared-mailbox
Read-onlyIdempotent

List emails or folders in a shared mailbox you can access, or enumerate its folder tree, to review shared messages read-only.

Instructions

List emails or folders in a shared mailbox the signed-in user can access (read-only). Returns messages from sharedMailbox (alias email) and folder (default inbox) with id/subject/from/receivedDateTime/preview, the same shape as search-emails list mode. folder takes a well-known name (inbox, sent, archive…), a custom/localized display name (e.g. Archiv), a nested path (e.g. Inbox/Vendors/Acme), or pass a raw folderId. listFolders: true enumerates the shared mailbox's folder tree (names, paths, IDs, counts), to find custom subfolders before reading them. Needs the mailbox delegated to the signed-in user in Exchange (admin-configured). outputVerbosity sets field count and count (default 25, max 50) page size. For search and filters over a shared mailbox, use search-emails with sharedMailbox set. Custom/localized names, nested paths and listFolders need the server opt-in setting OUTLOOK_SHARED_MAILBOX (work/school only); without it folder must be a well-known name or a folder ID.

Input Schema

NameRequiredDescriptionDefault
countNoNumber of emails to retrieve (default: 25, max: 50)
emailNoAlias for `sharedMailbox` (more intuitive name for the same value).
folderNoFolder to read from (default: inbox). Accepts a well-known name, a custom/localized display name, or a nested path like `Inbox/Subfolder`.
folderIdNoExact Graph folder ID to read from (e.g. from `listFolders`). Skips name resolution; takes precedence over `folder`.
listFoldersNoEnumerate the shared mailbox's full folder tree (names, paths, IDs, item counts) in place of reading messages.
sharedMailboxNoEmail address of the shared mailbox (required)
outputVerbosityNoOutput detail level (default: standard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.1
    • changedInput schema / properties / folder / description
      Previous value: -"Folder to read from (default: inbox)"New value: +"Folder to read from (default: inbox). Accepts a well-known name, a custom/localized display name, or a nested path like `Inbox/Subfolder`."
    • addedInput schema / properties / folderId
      Added value: +{
+  "description": "Exact Graph folder ID to read from (e.g. from `listFolders`). Skips name resolution; takes precedence over `folder`.",
+  "type": "string"
+}
    • addedInput schema / properties / listFolders
      Added value: +{
+  "description": "Enumerate the shared mailbox's full folder tree (names, paths, IDs, item counts) in place of reading messages.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv3.7.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / email
      Added value: +{
+  "description": "Alias for `sharedMailbox` (more intuitive name for the same value).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "sharedMailbox"
-]New value: +[]
  3. First observedv3.4.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the admin delegation prerequisite, the server opt-in OUTLOOK_SHARED_MAILBOX (work/school only), and the graceful degradation when it is absent (folder must be well-known name or ID).

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?

Dense but front-loaded: purpose first, then return shape, then folder semantics, then prerequisites and the opt-in caveat. Every sentence carries information, though the description is long enough that a couple of clauses could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description specifies the return shape (id/subject/from/receivedDateTime/preview, same as search-emails list mode) plus pagination via count. Combined with auth prerequisites and opt-in behavior, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: the accepted forms of `folder` (well-known, custom/localized, nested path, raw folderId), folderId precedence over folder, count default/max, and the OUTLOOK_SHARED_MAILBOX constraint on custom names. It largely mirrors rather than extends the schema on a few fields, keeping it at 4.

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

Purpose5/5

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

Opens with a specific verb+resource and scope: 'List emails or folders in a shared mailbox the signed-in user can access (read-only).' It also names the sibling it is not (search-emails for search/filters), so an agent can distinguish it 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 Guidelines5/5

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

Explicitly routes the agent: 'For search and filters over a shared mailbox, use search-emails with sharedMailbox set,' and explains when to use listFolders ('to find custom subfolders before reading them'). It also states the prerequisite that the mailbox must be delegated in Exchange (admin-configured).

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

Deploy Server

Other Tools