Skip to main content
Glama

Shared Mailbox

access-shared-mailbox
Read-onlyIdempotent

List emails or folders in a shared Outlook mailbox the signed-in user can access. Browse folder trees, read message details, or search a delegated mailbox (work/school accounts only).

Instructions

List emails or folders in a shared mailbox the signed-in user can access (read-only). Needs the server setting OUTLOOK_SHARED_MAILBOX (work/school only); while it is unset, every call is refused before any request to Microsoft Graph. Returns messages from sharedMailbox (alias email) and folder (default inbox) with id/subject/from/receivedDateTime/preview. 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 mailbox's folder tree (names, paths, IDs, counts). 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. search-emails with sharedMailbox searches and filters a shared mailbox.

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": "access-shared-mailbox"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the bar is lower, yet the description still adds real operational context: calls are refused before any Microsoft Graph request while the server setting is unset, and Exchange delegation by an admin is required. It stops short of describing pagination behavior or what the response envelope looks like, which keeps it at 4 rather than 5.

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 and front-loaded: purpose first, then the gating setting, then return fields, then folder semantics and the sibling alternative. A few clauses restate schema facts already visible to the agent (count default/max, outputVerbosity description), which is minor redundancy in an otherwise efficient single block.

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?

For a 7-parameter read tool with no output schema, the description covers what is returned (id/subject/from/receivedDateTime/preview), the folder-tree alternative, defaults, paging limits, configuration prerequisites and the delegation requirement. Nothing an agent needs to call it correctly or to predict a refusal 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 the baseline is 3, but the description goes beyond it: `folder` is documented as accepting well-known names, custom/localized display names ('Archiv'), and nested paths ('Inbox/Vendors/Acme'), and it states that `folderId` takes precedence over `folder`. `count` (default 25, max 50) and `outputVerbosity` are repeated from the schema rather than extended, so it is a strong 4, not a 5.

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 and resource ('List emails or folders in a shared mailbox'), states the scope constraint (only mailboxes the signed-in user can access) and the read-only nature. It also names the sibling it is not: 'search-emails with sharedMailbox searches and filters a shared mailbox,' so an agent can separate listing from searching without opening a 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 search/filter case to `search-emails` with `sharedMailbox`, and explains that `listFolders: true` substitutes folder-tree enumeration for message reading. Preconditions are given as gating rules (OUTLOOK_SHARED_MAILBOX must be set, work/school accounts only, mailbox must be delegated in Exchange), which is exactly the when-not guidance an agent needs.

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