m365-mcp

Forward Email

email_forward

Forward a Microsoft 365 email to recipients you name, with an optional note. Requires user approval via confirm=true and never infers recipients.

Instructions

Forward an email to recipients the user names, with an optional note. Requires confirm=true after the user approves. Never infer recipients from other context.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	Cc recipients.
`to`	Yes	Recipients.
`bcc`	No	Bcc recipients.
`comment`	No	Note above the forwarded message.
`confirm`	Yes	Must be true to forward this email; set only after the user approves.
`email_id`	Yes	Email to forward.
`account_id`	No	Account ID or email address. Omit when only one account is signed in.
`attachments`	No	Local files to attach: at most 10, each at most 25 MB.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes
`summary`	Yes	One-line human summary. The tool's text content is this result serialized as JSON (summary included), so a client that ignores structuredContent still sees every field.
`forwarded_id`	Yes
`recipient_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedv1.0.0Sep 29, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / account_id / description

Added value: +"Account ID or email address. Omit when only one account is signed in."

addedInput schema / properties / account_id / maxLength
```
Added value: +320
```
addedInput schema / properties / account_id / minLength
```
Added value: +1
```

addedInput schema / properties / attachments

Added value: +{
+  "description": "Local files to attach: at most 10, each at most 25 MB.",
+  "items": {
+    "description": "Local file path inside the server's allowed folders. Hidden and secret files are refused.",
+    "maxLength": 4096,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / bcc

Added value: +{
+  "description": "Bcc recipients.",
+  "items": {
+    "description": "Email address, e.g. jane@example.com.",
+    "format": "email",
+    "maxLength": 320,
+    "minLength": 3,
+    "type": "string"
+  },
+  "maxItems": 500,
+  "type": "array",
+  "uniqueItems": true
+}

removedInput schema / properties / body

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / cc / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / cc / default
```
Removed value: -null
```
addedInput schema / properties / cc / description
```
Added value: +"Cc recipients."
```

addedInput schema / properties / cc / items

Added value: +{
+  "description": "Email address, e.g. jane@example.com.",
+  "format": "email",
+  "maxLength": 320,
+  "minLength": 3,
+  "type": "string"
+}

addedInput schema / properties / cc / maxItems
```
Added value: +500
```
addedInput schema / properties / cc / type
```
Added value: +"array"
```
addedInput schema / properties / cc / uniqueItems
```
Added value: +true
```

addedInput schema / properties / comment

Added value: +{
+  "description": "Note above the forwarded message.",
+  "maxLength": 100000,
+  "type": "string"
+}

addedInput schema / properties / confirm / description

Added value: +"Must be true to forward this email; set only after the user approves."

addedInput schema / properties / email_id / description
```
Added value: +"Email to forward."
```
addedInput schema / properties / email_id / maxLength
```
Added value: +1024
```
addedInput schema / properties / email_id / minLength
```
Added value: +1
```

removedInput schema / properties / to / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]

addedInput schema / properties / to / description
```
Added value: +"Recipients."
```

addedInput schema / properties / to / items

Added value: +{
+  "description": "Email address, e.g. jane@example.com.",
+  "format": "email",
+  "maxLength": 320,
+  "minLength": 3,
+  "type": "string"
+}

addedInput schema / properties / to / maxItems
```
Added value: +500
```
addedInput schema / properties / to / minItems
```
Added value: +1
```
addedInput schema / properties / to / type
```
Added value: +"array"
```
addedInput schema / properties / to / uniqueItems
```
Added value: +true
```

changedInput schema / required

Previous value: -[
-  "account_id",
-  "email_id",
-  "to"
-]New value: +[
+  "email_id",
+  "to",
+  "confirm"
+]

addedOutput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties

Previous value: -{
-  "type": "string"
-}New value: +false

addedOutput schema / description
```
Added value: +"Forward confirmation."
```

addedOutput schema / properties

Added value: +{
+  "forwarded_id": {
+    "type": "string"
+  },
+  "recipient_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "status": {
+    "const": "sent"
+  },
+  "summary": {
+    "description": "One-line human summary. The tool's text content is this result serialized as JSON (summary included), so a client that ignores structuredContent still sees every field.",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "status",
+  "forwarded_id",
+  "recipient_count",
+  "summary"
+]

First observedv0.2.3Jun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare the write/non-idempotent/open-world profile, and the description adds genuinely non-structured behavior: an approval gate via confirm=true and an explicit prohibition on inferring recipients. Those are safety-relevant traits not derivable from the schema or annotations. It does not describe delivery outcome or failure modes.

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?

Three short sentences, each carrying a distinct constraint (action, approval gate, recipient-source prohibition). The core action is front-loaded with no filler.

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?

An output schema exists, so return values need no explanation. For an 8-parameter mutation tool, the description covers the action, the confirmation workflow, and the key safety constraint. An agent has everything needed to invoke it correctly.

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 (cc, bcc, comment, email_id, account_id, attachments) is already documented. The description only reinforces the confirm semantics, which the schema also states, so it adds little beyond the baseline.

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?

Specific verb (Forward) plus resource (an email) plus the qualifying detail that recipients are user-named and the note is optional. This cleanly separates it from email_send and email_reply, which an agent can distinguish without opening any schema.

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 real usage conditions: confirm=true is required and only after user approval, and recipients must never be inferred from other context. That is a clear when-to-use and a hard when-not rule. It stops short of naming the sibling alternatives (email_send/email_reply) for the non-forward cases.

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