Skip to main content
Glama

send_message

Send emails to recipients with options for subject, body, CC, BCC, and thread association using the Gmail MCP server.

Instructions

Send an email message to specified recipients. Note the mechanics of the raw parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoThe entire email message in base64url encoded RFC 2822 format, ignores params.to, cc, bcc, subject, body, includeBodyHtml if provided
threadIdNoThe thread ID to associate this message with
toNoList of recipient email addresses
ccNoList of CC recipient email addresses
bccNoList of BCC recipient email addresses
subjectNoThe subject of the email
bodyNoThe body of the email
includeBodyHtmlNoWhether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large

Implementation Reference

  • The handler function for the 'send_message' tool. It handles OAuth, constructs the raw email if not provided, sends the message via Gmail API, processes the response payload to decode bodies and filter headers, and formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        let raw = params.raw
        if (!raw) raw = await constructRawMessage(gmail, params)
    
        const messageSendParams: MessageSendParams = { userId: 'me', requestBody: { raw } }
        if (params.threadId && messageSendParams.requestBody) {
          messageSendParams.requestBody.threadId = params.threadId
        }
    
        const { data } = await gmail.users.messages.send(messageSendParams)
    
        if (data.payload) {
          data.payload = processMessagePart(
            data.payload,
            params.includeBodyHtml
          )
        }
    
        return formatResponse(data)
      })
    }
  • Input schema (Zod) for the 'send_message' tool defining parameters like raw message, recipients, subject, body, etc.
      raw: z.string().optional().describe("The entire email message in base64url encoded RFC 2822 format, ignores params.to, cc, bcc, subject, body, includeBodyHtml if provided"),
      threadId: z.string().optional().describe("The thread ID to associate this message with"),
      to: z.array(z.string()).optional().describe("List of recipient email addresses"),
      cc: z.array(z.string()).optional().describe("List of CC recipient email addresses"),
      bcc: z.array(z.string()).optional().describe("List of BCC recipient email addresses"),
      subject: z.string().optional().describe("The subject of the email"),
      body: z.string().optional().describe("The body of the email"),
      includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large")
    },
  • src/index.ts:607-641 (registration)
    Registration of the 'send_message' tool using server.tool(), including name, description, input schema, and handler function.
    server.tool("send_message",
      "Send an email message to specified recipients. Note the mechanics of the raw parameter.",
      {
        raw: z.string().optional().describe("The entire email message in base64url encoded RFC 2822 format, ignores params.to, cc, bcc, subject, body, includeBodyHtml if provided"),
        threadId: z.string().optional().describe("The thread ID to associate this message with"),
        to: z.array(z.string()).optional().describe("List of recipient email addresses"),
        cc: z.array(z.string()).optional().describe("List of CC recipient email addresses"),
        bcc: z.array(z.string()).optional().describe("List of BCC recipient email addresses"),
        subject: z.string().optional().describe("The subject of the email"),
        body: z.string().optional().describe("The body of the email"),
        includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          let raw = params.raw
          if (!raw) raw = await constructRawMessage(gmail, params)
    
          const messageSendParams: MessageSendParams = { userId: 'me', requestBody: { raw } }
          if (params.threadId && messageSendParams.requestBody) {
            messageSendParams.requestBody.threadId = params.threadId
          }
    
          const { data } = await gmail.users.messages.send(messageSendParams)
    
          if (data.payload) {
            data.payload = processMessagePart(
              data.payload,
              params.includeBodyHtml
            )
          }
    
          return formatResponse(data)
        })
      }
    )
  • Key helper function to construct the raw RFC 2822 email message in base64url format, handling headers, body, thread quoting, and text wrapping.
    const constructRawMessage = async (gmail: gmail_v1.Gmail, params: NewMessage) => {
      let thread: Thread | null = null
      if (params.threadId) {
        const threadParams = { userId: 'me', id: params.threadId, format: 'full' }
        const { data } = await gmail.users.threads.get(threadParams)
        thread = data
      }
    
      const message = []
      if (params.to?.length) message.push(`To: ${wrapTextBody(params.to.join(', '))}`)
      if (params.cc?.length) message.push(`Cc: ${wrapTextBody(params.cc.join(', '))}`)
      if (params.bcc?.length) message.push(`Bcc: ${wrapTextBody(params.bcc.join(', '))}`)
      if (thread) {
        message.push(...getThreadHeaders(thread).map(header => wrapTextBody(header)))
      } else if (params.subject) {
        message.push(`Subject: ${wrapTextBody(params.subject)}`)
      } else {
        message.push('Subject: (No Subject)')
      }
      message.push('Content-Type: text/plain; charset="UTF-8"')
      message.push('Content-Transfer-Encoding: quoted-printable')
      message.push('MIME-Version: 1.0')
      message.push('')
    
      if (params.body) message.push(wrapTextBody(params.body))
    
      if (thread) {
        const quotedContent = getQuotedContent(thread)
        if (quotedContent) {
          message.push('')
          message.push(wrapTextBody(quotedContent))
        }
      }
    
      return Buffer.from(message.join('\r\n')).toString('base64url').replace(/\+/g, '-').replace(/\//g, '_').replace(/=+$/, '')
    }
  • Shared helper that handles OAuth2 authentication, client creation, credential validation, and executes the Gmail API call, catching errors.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the 'mechanics of the raw parameter,' which adds some context about a specific behavior (that 'raw' overrides other parameters), but fails to cover critical aspects: it doesn't specify whether this is a read-only or destructive operation, what permissions are required, how errors are handled, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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?

The description is very concise—just two sentences—with no wasted words. It front-loads the core purpose and adds a specific note about parameter behavior. However, the second sentence is somewhat cryptic ('Note the mechanics of the raw parameter') without elaboration, which slightly reduces clarity but doesn't detract from overall efficiency.

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?

Given the complexity (8 parameters, no annotations, no output schema), the description is insufficient. It covers the basic purpose and hints at one parameter's behavior but omits critical details: it doesn't explain what happens on success/failure, what the return value is, or how this tool differs from siblings like 'send_draft'. For a mutation tool with rich parameters, more context is needed to guide effective use.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description adds minimal value beyond the schema by noting the 'mechanics of the raw parameter' (i.e., that it overrides other fields), which provides some semantic insight. However, it doesn't elaborate on parameter interactions or usage examples, so it meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Send an email message to specified recipients.' It provides a specific verb ('Send') and resource ('email message'), making the action clear. However, it doesn't explicitly differentiate this from sibling tools like 'send_draft' or 'create_draft', which is why it doesn't achieve a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers minimal guidance on when to use this tool. It mentions 'Note the mechanics of the raw parameter,' which hints at a specific use case for advanced users, but doesn't provide explicit when-to-use or when-not-to-use advice compared to alternatives like 'send_draft' or 'create_draft'. No prerequisites or contextual usage rules are stated.

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/HitmanLy007/gmail-mcp'

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