Skip to main content
Glama
kojott

mailmcp

by kojott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Forward a message

forward_message
Destructive

Forward email messages with attachments directly from your mailbox, without routing files through chat. Add an optional comment, respect send allowlist, or save as draft.

Instructions

Forwards a message including all its attachments, without the files passing through the chat. Optional comment goes above the forwarded text. Recipients must match send_allowlist; with as_draft the forward is saved to Drafts instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toYes
bccNo
uidYesuid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned
folderNoFolder/label path. Defaults to All Mail on Gmail, INBOX elsewhere.
accountYesAccount id from list_accounts
commentNoText to put above the forwarded message
subjectNoDefaults to "Fwd: <original subject>"
as_draftNoSave to Drafts instead of sending
include_attachmentsNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.8.1
    • addedInput schema / properties / uid / description
      Added value: +"uid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned"
    • addedInput schema / properties / uid / maxLength
      Added value: +512
    • removedInput schema / properties / uid / maximum
      Removed value: -9007199254740991
    • addedInput schema / properties / uid / minLength
      Added value: +1
    • removedInput schema / properties / uid / minimum
      Removed value: -1
    • changedInput schema / properties / uid / type
      Previous value: -"integer"New value: +"string"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description does not need to repeat mutation. It adds meaningful context: attachments bypass chat, recipients must match allowlist, and as_draft changes the behavior to saving a draft. This goes beyond annotations without contradicting them.

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?

The description is three sentences with no filler. The core action and key differentiators are front-loaded, and every sentence earns its place. It is efficiently structured for quick parsing.

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

Completeness4/5

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

Given 10 parameters and no output schema, the description covers the most important behaviors (attachment handling, allowlist, draft behavior). It does not explain the sending mechanism or default subject, but the schema covers many defaults. The description is sufficient for an agent to make a correct call.

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 70%, so many parameters already have descriptions. The description adds context for comment ('goes above the forwarded text') and as_draft ('saved to Drafts'), and notes the allowlist requirement for recipients. This provides some extra meaning but does not comprehensively cover all parameters.

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?

The description states a specific verb and resource ('Forwards a message') and highlights a key differentiator: 'without the files passing through the chat.' It also mentions optional comment and as_draft behavior, distinguishing it from send_message and reply_send. This is clear and unambiguous.

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?

The description implies usage (forwarding a message) but does not explicitly contrast with alternatives like reply_send or send_message. It mentions the send_allowlist constraint and as_draft, but no 'use this when' or 'instead of' guidance. The context is implicit rather than explicit.

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