Skip to main content
Glama
gmail-mcp
by gchallen

forward

Send an existing email onward with a comment above the original, reattach attachments, and send immediately or save as a draft.

Instructions

Forward a message: your comment on top, then the standard "Forwarded message" block with the original headers and body, with the original attachments re-attached (includeAttachments false to drop them). Subject prefixed with Fwd:. Sends immediately unless asDraft 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": {
      "messageId": "<messageId>",
      "to": "<to>"
    },
    "name": "forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyNoComment placed above the forwarded message. Plain-text body. One line per paragraph, no hard wrapping; Gmail wraps on display and links bare URLs. Markdown does NOT render: for bullets or other formatting supply htmlBody instead.
asDraftNoCreate a draft instead of sending. Default false.
htmlBodyNoHTML body, used when the message needs formatting such as <ul><li> lists. When given, "body" becomes the plain-text alternative (derived from the HTML if omitted). Do not include the signature; it is appended.
messageIdYes
signatureNoSet false to send without the configured signature. By default the signature (from config.json, GMAIL_SIGNATURE, or the Gmail settings signature) is appended once; a copy typed into the body is de-duplicated.
attachmentsNoAdditional files to attach.
includeAttachmentsNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4.2/5.0
Behavior4/5

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

With annotations declaring non-read-only, open-world, non-destructive, the description still adds real behavioral context beyond them: immediate sending unless asDraft, an automatic Fwd: subject prefix, original attachments carried over, and the forwarded-block structure. It stops short of describing failure modes or what a successful call returns, but the mutation and side effects are clearly disclosed.

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 tight sentences, front-loaded with the core action and its output shape, then the send semantics, then the subject convention. Every clause carries information; nothing is restated from the name or annotations.

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?

For a 10-parameter, 2-required mutation tool with no output schema, the description covers the essential call semantics: what gets sent, when it sends, and what the recipient sees. It is slightly thin on error behavior and on the addressing parameters, but the annotations plus schema description largely fill that gap.

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?

At 60% schema coverage the description meaningfully adds to structured fields: it explains that includeAttachments=false drops the re-attached originals (the schema only says "Default true"), and it frames body/htmlBody in terms of the forwarded layout and comment placement. It says nothing about cc/bcc or the attachments parameter, so coverage of the remaining parameters is left entirely to the schema.

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 ("Forward a message") and immediately spells out the resulting composition: a user comment on top, the standard "Forwarded message" block with original headers and body, and re-attached attachments. That detail makes it unmistakable versus reply, send_message, or create_draft, so an agent can select it without opening the schema.

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 context is implied rather than stated: "Sends immediately unless asDraft is true" tells the agent it is a send-path tool and gives one explicit opt-out, but there is no guidance on when to choose forward over reply or send_message, nor on prerequisites such as a valid messageId.

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