Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

draft_gmail_message

Create a new draft email or a reply draft in Gmail with optional HTML formatting, recipients, and threading support.

Instructions

Creates a draft email in the user's Gmail account. Supports both new drafts and reply drafts.

Args: user_google_email (str): The user's Google email address. Required. subject (str): Email subject. body (str): Email body (plain text). body_format (Literal['plain', 'html']): Email body format. Defaults to 'plain'. to (Optional[str]): Optional recipient email address. Can be left empty for drafts. cc (Optional[str]): Optional CC email address. bcc (Optional[str]): Optional BCC email address. thread_id (Optional[str]): Optional Gmail thread ID to reply within. When provided, creates a reply draft. in_reply_to (Optional[str]): Optional Message-ID of the message being replied to. Used for proper threading. references (Optional[str]): Optional chain of Message-IDs for proper threading. Should include all previous Message-IDs.

Returns: str: Confirmation message with the created draft's ID.

Examples: # Create a new draft draft_gmail_message(subject="Hello", body="Hi there!", to="user@example.com")

# Create a plaintext draft with CC and BCC
draft_gmail_message(
    subject="Project Update",
    body="Here's the latest update...",
    to="user@example.com",
    cc="manager@example.com",
    bcc="archive@example.com"
)

# Create a HTML draft with CC and BCC
draft_gmail_message(
    subject="Project Update",
    body="<strong>Hi there!</strong>",
    body_format="html",
    to="user@example.com",
    cc="manager@example.com",
    bcc="archive@example.com"
)

# Create a reply draft in plaintext
draft_gmail_message(
    subject="Re: Meeting tomorrow",
    body="Thanks for the update!",
    to="user@example.com",
    thread_id="thread_123",
    in_reply_to="<message123@gmail.com>",
    references="<original@gmail.com> <message123@gmail.com>"
)

# Create a reply draft in HTML
draft_gmail_message(
    subject="Re: Meeting tomorrow",
    body="<strong>Thanks for the update!</strong>",
    body_format="html,
    to="user@example.com",
    thread_id="thread_123",
    in_reply_to="<message123@gmail.com>",
    references="<original@gmail.com> <message123@gmail.com>"
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
subjectYesEmail subject.
bodyYesEmail body (plain text).
body_formatNoEmail body format. Use 'plain' for plaintext or 'html' for HTML content.plain
toNoOptional recipient email address.
ccNoOptional CC email address.
bccNoOptional BCC email address.
thread_idNoOptional Gmail thread ID to reply within.
in_reply_toNoOptional Message-ID of the message being replied to.
referencesNoOptional chain of Message-IDs for proper threading.
dry_runNoIf True, returns a preview and does not create the draft. Defaults to True.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The description omits the 'dry_run' parameter, which defaults to true and controls whether an actual draft is created or just a preview. This is a critical behavioral detail not disclosed. No annotations are provided, so the description carries full burden but fails to be transparent.

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 well-structured with a summary, parameter list, returns, and examples. The examples are comprehensive but somewhat verbose. The omission of the 'dry_run' parameter from the parameter list is a structural flaw.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, 3 required, and no annotations, the description covers most parameters with good detail. However, the missing 'dry_run' parameter and lack of information about side effects or rate limits leave gaps. The output schema is mentioned but not detailed.

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?

The description adds value beyond the schema by explaining threading parameters (thread_id, in_reply_to, references) and providing examples. However, it omits the 'dry_run' parameter entirely, which is a significant gap. Schema coverage is 91% but the missing parameter lowers the score.

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 clearly states it creates a draft email in the user's Gmail account, supporting both new and reply drafts. It distinguishes from sibling tools like 'send_gmail_message' and 'modify_gmail_message_labels' by its focus on drafting.

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 provides detailed parameters and examples covering various usage scenarios (new draft, reply draft, with CC/BCC, HTML body). However, it lacks explicit guidance on when to use this tool versus alternatives like 'send_gmail_message' or when not to use it.

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/Skeptomenos/google-workspace-mcp-advanced'

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