Skip to main content
Glama
gmail-mcp
by gchallen

send_message

Sends a new Gmail message immediately, including replies threaded by message or thread ID, or sends an existing draft when only a draft ID is provided.

Instructions

Send a new message immediately. To thread it into an existing conversation give replyToMessageId (quotes and threads on that message) or replyThreadId (threads only). To send a draft instead, give draftId and nothing else. For replies with Gmail's default recipients use the reply tool. Prefer create_draft when the user should review first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toNo
bccNo
bodyNoPlain-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.
quoteNoWhen replyToMessageId is set, quote it below the new text. Default true.
draftIdNoSend this existing draft; all other fields are ignored.
subjectNoTitle Case.
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.
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.
attachmentsNoFiles to attach, as local paths (preferred: any size up to Gmail's 25 MB total) or base64 objects.
replyThreadIdNo
replyToMessageIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful but limited fact that draftId excludes all other fields and that quoting defaults on. It does not mention the 25 MB attachment ceiling, signature auto-append, or any send-rate behavior beyond what the schema already states.

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?

Four short sentences, front-loaded with the core action, then threading, then draft mode, then alternatives. No restatement of the tool name or filler.

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 12-parameter mutation tool with no output schema, the description covers the mutually exclusive send modes and points to the right siblings. It leaves the compose fields to the schema, which is reasonable, though a note on what a successful send returns or on attachment size limits would close the remaining 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?

Schema coverage is 58%, and the two most ambiguous parameters, replyToMessageId and replyThreadId, have no schema descriptions at all; the definition supplies exactly that distinction (quote+thread vs. thread only). The draftId exclusivity rule is also clarified here rather than in the schema. Remaining gaps are minor because cc/to/bcc/body/attachments are well documented in 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: 'Send a new message immediately.' It distinguishes itself from send_draft and create_draft by naming the draft-send mode and the review-first alternative, so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit conditional guidance: replyToMessageId for quoting and threading, replyThreadId for threading only, draftId to send an existing draft, the reply tool for default recipients, and create_draft when the user should review first. These are named alternatives with the exact condition that selects each.

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