Skip to main content
Glama

send_message

Send emails through Gmail by specifying recipients, subject, body, and attachments. Manage CC/BCC recipients and associate messages with existing threads.

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 calls handleTool to authenticate, constructs a raw email message if not provided using constructRawMessage, sends it using the Gmail API's users.messages.send method, processes the response payload with processMessagePart if includeBodyHtml is specified, 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, threadId, to, cc, bcc, subject, body, and includeBodyHtml.
      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:640-674 (registration)
    Registration of the 'send_message' tool on the MCP server using server.tool(), including description, input schema, and inline 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)
        })
      }
    )
  • Helper function constructRawMessage used by send_message to build the base64url-encoded raw RFC 2822 email message, handling recipients, subject, body, threading with quotes and headers.
    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(/=+$/, '')
    }
  • Core helper handleTool wraps API calls with OAuth2 client creation, credential validation, Gmail client setup, error handling (especially auth errors), and response formatting. Used by send_message.
    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) {
        // Check for specific authentication errors
        if (
          error.message?.includes("invalid_grant") ||
          error.message?.includes("refresh_token") ||
          error.message?.includes("invalid_client") ||
          error.message?.includes("unauthorized_client") ||
          error.code === 401 ||
          error.code === 403
        ) {
          return formatResponse({
            error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`,
          });
        }
    
        return formatResponse({ error: `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 parameter interaction, but fails to describe critical behaviors such as whether this is a read/write operation, potential side effects (e.g., email delivery, rate limits), or error handling. This leaves significant gaps for a mutation tool.

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 brief and to the point, consisting of two sentences that directly address the tool's purpose and a key parameter detail. It avoids unnecessary fluff, though it could be slightly more structured by front-loading the main purpose more clearly.

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 of an email-sending tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., permissions, side effects), usage context, and output expectations, making it incomplete for effective agent 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%, so the schema already documents all 8 parameters thoroughly. The description adds minimal value by noting the mechanics of the 'raw' parameter, but doesn't provide additional semantic context beyond what's in the schema, such as examples or edge cases. This 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 action ('send an email message') and resource ('to specified recipients'), which is specific and unambiguous. However, it doesn't explicitly differentiate this tool from sibling tools like 'send_draft' or 'create_draft', which also involve sending emails, so it doesn't reach the highest 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 provides no guidance on when to use this tool versus alternatives like 'send_draft' or 'create_draft', nor does it mention any prerequisites or context for usage. It only hints at a parameter mechanic without broader usage context.

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

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