Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_forward

Forward an email to new recipients with optional CC/BCC, custom body, and extra files; original attachments are omitted unless explicitly included.

Instructions

Forward an email to new recipients. The original message's attachments are left out unless includeOriginalAttachments is true

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": {
      "accountId": "<accountId>",
      "emailId": "<emailId>",
      "to": "<to>"
    },
    "name": "email_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyNo
emailIdYes
accountIdYes
signatureNoAdd the account's signature (default true). Gmail: the signature of the send-as address the mail goes out from, read from Gmail's settings, in Gmail's own markup above any quoted history; a body that already holds one is left alone. Outlook.com, iCloud and IMAP have no signature a client can read, so nothing is added there. The result's `signature` field says what happened
attachmentsNoFiles to attach to the forward. Total size, together with forwarded original attachments, is capped at 25 MB
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)
includeOriginalAttachmentsNoAlso forward the original message's attachments (default false). Leave it off unless the user asked for the files to go along

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one meaningful default: original attachments are dropped unless includeOriginalAttachments is set. It says nothing about whether the forward is sent immediately, what permissions are needed, the 25 MB size cap, signature injection, or the restrictions on attachment paths, all of which are mutation-relevant.

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?

Two short sentences, front-loaded with the action and followed by the one non-obvious default. Nothing is wasted, though the trailing clause restates a default already encoded in the schema's boolean parameter.

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

Completeness2/5

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

This is a 10-parameter, nested-object mutation with no annotations and no output schema, yet the description covers only the attachment-default nuance. An agent still lacks guidance on send semantics, account/email identification, signature behavior, and attachment sourcing for a tool that actually dispatches mail.

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

Parameters2/5

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

Schema description coverage is only 40% across 10 parameters, so the description should compensate but largely does not. The single parameter it mentions, includeOriginalAttachments, is already documented in the schema, leaving to/cc/bcc/body/emailId/accountId without any added meaning from the description.

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?

The description names a specific verb and resource ('Forward an email to new recipients'), which is unambiguous and distinguishable from nearby tools like email_reply or email_draft_create by implication of the verb. It does not explicitly contrast itself with those siblings, so it stops 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?

Usage is only implied: an agent can infer this is the tool for redirecting a received message to new addresses rather than replying or composing a draft. There is no explicit when-to-use or when-not-to-use statement, and no mention of prerequisites such as which account or folder the email must live in.

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