Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Send Gmail Message

send_gmail_message

Send emails through Gmail: compose new messages, reply to threads, forward existing emails, add attachments, and use alias addresses.

Instructions

Sends an email using the user's Gmail account. Supports new emails, replies, and forwards, with optional attachments. Supports Gmail's "Send As" feature to send from configured alias addresses.

To forward an existing message, pass forward_message_id. The original subject, body (quoted with a "Forwarded message" header), and attachments are carried over. In forward mode, body (if any) is prepended as a note and subject is optional. Threading, reply, and signature options do not apply when forwarding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoOptional CC email address.
toNoRecipient email address. Optional when replying with reply_all=True, which derives it from the thread.
bccNoOptional BCC email address.
bodyNoEmail body content (plain text or HTML). Required when sending. When forwarding, this is an optional note prepended above the quoted original.
subjectNoEmail subject. Required when sending; optional when forwarding (defaults to 'Fwd: <original subject>').
from_nameNoOptional sender display name (e.g., 'Peter Hartree'). If provided, the From header will be formatted as 'Name <email>'.
reply_allNoWhether to derive reply-all recipients from the thread: To = the sender being replied to, Cc = the other participants, excluding the authenticated account and from_email. Requires thread_id. Explicit to/cc win; when cc is omitted the sender being replied to is added to the derived Cc if they are not already in To. Defaults to false.
thread_idNoOptional Gmail thread ID to reply within. When in_reply_to is omitted, replies to the latest non-draft, non-trash message with an RFC Message-ID.
from_emailNoOptional 'Send As' alias email address. Must be configured in Gmail settings (Settings > Accounts > Send mail as). If not provided, uses the authenticated user's email.
referencesNoOptional Message-ID ancestry chain. Normally omit when thread_id is provided; the server derives the chain through the selected reply target.
attachmentsNoOptional list of attachments. Each can have: "url" (fetch from URL — works with MCP attachment URLs from get_drive_file_download_url / get_gmail_attachment_content), OR "path" (file path, auto-encodes), OR "content" (standard base64, not urlsafe) + "filename". Optional "mime_type". Optional "content_id" (string) makes the attachment inline-rendered: it lands in a multipart/related part with `Content-ID: <content_id>` and `Content-Disposition: inline`, and the HTML body can reference it via `<img src="cid:<content_id>">` (RFC 2392). Without `content_id` the attachment is a regular multipart/mixed attachment. Example: [{"url": "https://host/attachments/abc-123", "filename": "report.pdf"}]
body_formatNoFormat of the body content (and of the prepended note when forwarding). Use 'plain' for plaintext or 'html' for HTML content.plain
in_reply_toNoOptional RFC Message-ID to explicitly reply to a specific message (e.g., '<message123@gmail.com>'). Omit to reply to the latest eligible message in thread_id.
quote_originalNoWhether to include the message being replied to as a quoted original. Only has an effect when thread_id is provided. Defaults to false.
include_signatureNoWhether to append the Gmail signature from Settings > Signature when available. Defaults to true.
user_google_emailYesThe user's Google email address. Required for authentication.
forward_message_idNoSet to a Gmail message ID to forward that message instead of composing a new one. The original subject, body, and (optionally) attachments are carried over; 'body' becomes an optional note prepended to the forward.
include_forwarded_attachmentsNoWhen forwarding, whether to include the original message's attachments. Ignored unless forward_message_id is set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv1.25.2
    • changedInput schema / properties / in_reply_to / description
      Previous value: -"Optional RFC Message-ID of the message being replied to (e.g., '<message123@gmail.com>')."New value: +"Optional RFC Message-ID to explicitly reply to a specific message (e.g., '<message123@gmail.com>'). Omit to reply to the latest eligible message in thread_id."
    • changedInput schema / properties / references / description
      Previous value: -"Optional chain of Message-IDs for proper threading."New value: +"Optional Message-ID ancestry chain. Normally omit when thread_id is provided; the server derives the chain through the selected reply target."
    • changedInput schema / properties / thread_id / description
      Previous value: -"Optional Gmail thread ID to reply within."New value: +"Optional Gmail thread ID to reply within. When in_reply_to is omitted, replies to the latest non-draft, non-trash message with an RFC Message-ID."
  2. Changed7 schema fields changedv1.24.0
    • addedInput schema / properties / quote_original
      Added value: +{
      +  "default": false,
      +  "description": "Whether to include the message being replied to as a quoted original. Only has an effect when thread_id is provided. Defaults to false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / reply_all
      Added value: +{
      +  "default": false,
      +  "description": "Whether to derive reply-all recipients from the thread: To = the sender being replied to, Cc = the other participants, excluding the authenticated account and from_email. Requires thread_id. Explicit to/cc win; when cc is omitted the sender being replied to is added to the derived Cc if they are not already in To. Defaults to false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / to / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / to / default
      Added value: +null
    • changedInput schema / properties / to / description
      Previous value: -"Recipient email address."New value: +"Recipient email address. Optional when replying with reply_all=True, which derives it from the thread."
    • removedInput schema / properties / to / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "user_google_email",
      -  "to"
      -]New value: +[
      +  "user_google_email"
      +]
  3. Changed30 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / attachments
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional list of attachments. Each can have: \"url\" (fetch from URL — works with MCP attachment URLs from get_drive_file_download_url / get_gmail_attachment_content), OR \"path\" (file path, auto-encodes), OR \"content\" (standard base64, not urlsafe) + \"filename\". Optional \"mime_type\". Optional \"content_id\" (string) makes the attachment inline-rendered: it lands in a multipart/related part with `Content-ID: <content_id>` and `Content-Disposition: inline`, and the HTML body can reference it via `<img src=\"cid:<content_id>\">` (RFC 2392). Without `content_id` the attachment is a regular multipart/mixed attachment. Example: [{\"url\": \"https://host/attachments/abc-123\", \"filename\": \"report.pdf\"}]"
      +}
    • addedInput schema / properties / bcc
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional BCC email address."
      +}
    • addedInput schema / properties / body / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / body / default
      Added value: +null
    • changedInput schema / properties / body / description
      Previous value: -"Email body (plain text)."New value: +"Email body content (plain text or HTML). Required when sending. When forwarding, this is an optional note prepended above the quoted original."
    • removedInput schema / properties / body / title
      Removed value: -"Body"
    • removedInput schema / properties / body / type
      Removed value: -"string"
    • addedInput schema / properties / body_format
      Added value: +{
      +  "default": "plain",
      +  "description": "Format of the body content (and of the prepended note when forwarding). Use 'plain' for plaintext or 'html' for HTML content.",
      +  "enum": [
      +    "plain",
      +    "html"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / cc
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional CC email address."
      +}
    • addedInput schema / properties / forward_message_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Set to a Gmail message ID to forward that message instead of composing a new one. The original subject, body, and (optionally) attachments are carried over; 'body' becomes an optional note prepended to the forward."
      +}
    • addedInput schema / properties / from_email
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional 'Send As' alias email address. Must be configured in Gmail settings (Settings > Accounts > Send mail as). If not provided, uses the authenticated user's email."
      +}
    • addedInput schema / properties / from_name
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional sender display name (e.g., 'Peter Hartree'). If provided, the From header will be formatted as 'Name <email>'."
      +}
    • addedInput schema / properties / in_reply_to
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional RFC Message-ID of the message being replied to (e.g., '<message123@gmail.com>')."
      +}
    • addedInput schema / properties / include_forwarded_attachments
      Added value: +{
      +  "default": true,
      +  "description": "When forwarding, whether to include the original message's attachments. Ignored unless forward_message_id is set.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_signature
      Added value: +{
      +  "default": true,
      +  "description": "Whether to append the Gmail signature from Settings > Signature when available. Defaults to true.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / references
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional chain of Message-IDs for proper threading."
      +}
    • removedInput schema / properties / service
      Removed value: -{
      -  "title": "service",
      -  "type": "string"
      -}
    • addedInput schema / properties / subject / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / subject / default
      Added value: +null
    • changedInput schema / properties / subject / description
      Previous value: -"Email subject."New value: +"Email subject. Required when sending; optional when forwarding (defaults to 'Fwd: <original subject>')."
    • removedInput schema / properties / subject / title
      Removed value: -"Subject"
    • removedInput schema / properties / subject / type
      Removed value: -"string"
    • addedInput schema / properties / thread_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Gmail thread ID to reply within."
      +}
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • addedInput schema / properties / user_google_email / description
      Added value: +"The user's Google email address. Required for authentication."
    • removedInput schema / properties / user_google_email / title
      Removed value: -"User Google Email"
    • changedInput schema / required
      Previous value: -[
      -  "service",
      -  "user_google_email",
      -  "to",
      -  "subject",
      -  "body"
      -]New value: +[
      +  "user_google_email",
      +  "to"
      +]
    • removedInput schema / title
      Removed value: -"send_gmail_messageArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object",
      +  "x-fastmcp-wrap-result": true
      +}
  4. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate this is a mutating, non-idempotent operation, but the description adds useful behavioral detail: forward mode carries over the original subject, quotes the body with a 'Forwarded message' header, optionally includes attachments, and disables threading/reply/signature options. This goes beyond the annotations and helps the agent predict side effects. There is no contradiction with the annotations.

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 compact and front-loaded: the first sentence states the core action, followed by a focused paragraph on forward-mode behavior. Every sentence earns its place, with no filler or repetition of schema details.

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?

Given the tool's complexity (18 parameters, multiple modes), the description provides a solid orientation to new/reply/forward and alias sending, while the highly detailed schema covers the remaining parameter-level semantics. An output schema exists, so the description does not need to explain return values. No critical calling context is missing for an agent to use this tool correctly.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter semantics not fully captured in individual property descriptions: how forward mode treats body as a prepended note, which options are ignored, and the overall relationship between forward_message_id, subject, and body. This helps an agent reason about combinations of 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: it 'Sends an email using the user's Gmail account.' It clearly identifies the main modes (new, reply, forward), attachments, and the 'Send As' alias feature, which distinguishes it from siblings like draft_gmail_message and the Chat-oriented send_message. An agent can immediately understand what this tool accomplishes.

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?

The description gives concrete usage direction for forwarding: pass forward_message_id, and explains that the original subject/body/attachments are carried over and that body becomes an optional note. It also notes which options do not apply when forwarding. However, it does not explicitly contrast this tool with draft_gmail_message or state when to prefer a reply versus a new message, leaving some selection inference to the reader.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server