Skip to main content
Glama

graph_list_mail_attachments

List attachments on an Outlook email message by message ID, optionally targeting a shared mailbox, to identify files before downloading or processing them.

Instructions

List attachments on an email message.

Args: message_id: The email message ID. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message_id": "<message_id>"
    },
    "name": "graph_list_mail_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.4/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 burden. It usefully discloses that the mailbox parameter requires delegated Mail.*.Shared permissions and that an empty value targets your own mailbox, but it says nothing about what is returned (attachment metadata vs. content), pagination, or error behavior for a missing message.

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?

One-line purpose statement followed by a compact Args block; every sentence carries information and the purpose is front-loaded. No filler or restatement of the tool name.

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 two-parameter read tool with no output schema, the description covers both parameters and the permission model, which is most of what is needed. It stops short of describing the shape of the returned attachment list or pagination, leaving a gap an agent would want when consuming results.

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 description coverage is 0%, so the description must compensate, and it largely does: message_id is identified as the email message ID, and mailbox is explained as a shared mailbox address or user ID with an empty default meaning your own mailbox, plus its permission requirement. Only the format of message_id (opaque Graph ID) is left implicit.

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 attachments on an email message.' An agent can distinguish it from graph_get_mail_attachment by the plural 'list' framing, but the description never names that sibling or otherwise differentiates explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. It does not say to use this to enumerate attachments before calling graph_get_mail_attachment for content, nor does it mention any alternative. The only contextual note is a permission prerequisite, which is not usage guidance.

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