Skip to main content
Glama
dipseth

google-workspace-unlimited

Draft Gmail Reply

draft_gmail_reply

Draft a reply to a specific Gmail message with proper threading. Supports plain text, HTML, or mixed content and customizable recipients.

Instructions

Create a draft reply to a specific Gmail message with proper threading and HTML support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCustom CC recipients (when reply_mode='custom')
toNoCustom recipients (when reply_mode='custom')
bccNoCustom BCC recipients (when reply_mode='custom')
bodyYesDraft reply body content. Usage depends on content_type: 'plain' = plain text only, 'html' = HTML content (plain auto-generated), 'mixed' = plain text (HTML in html_body). Original message will be automatically quoted
html_bodyNoHTML content when content_type='mixed'. The original message will be automatically quoted in HTML format. Ignored for 'plain' and 'html' types
message_idYesThe ID of the original Gmail message to draft a reply for. This maintains proper email threading in the draft
reply_modeNoWho receives the reply: 'sender_only' = only original sender (default), 'reply_all' = all original recipients, 'custom' = use provided to/cc/bcc parameterssender_only
content_typeNoContent type: 'plain' (text only with quoted original), 'html' (HTML in body param with quoted original), 'mixed' (text in body, HTML in html_body, both with quoted original)mixed
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
subjectNo
successYes
draft_idNo
thread_idNo
userEmailYes
replied_toNo
reply_modeNo
content_typeYes
cc_recipientsNo
to_recipientsNo
bcc_recipientsNo
original_message_idYes
Behavior4/5

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

Annotations already indicate it's not read-only or destructive. Description adds value by specifying threading and HTML support, but could explicitly note that it only creates a draft and does not send the email.

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?

A single, efficient sentence of 15 words that captures the essential purpose with no wasted words.

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?

Given the complexity of the tool (9 parameters, 2 enums, output schema present), the combination of a brief description and detailed schema provides adequate completeness. Minor gap: does not mention that the draft is saved to Gmail.

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?

Schema coverage is 100%, and the schema includes detailed descriptions for all parameters. The description does not add significant additional parameter-level meaning beyond 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?

The description clearly states the tool creates a draft reply to a specific Gmail message with proper threading and HTML support. It distinguishes from siblings like draft_gmail_forward (forward) and reply_to_gmail_message (send reply).

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

Usage Guidelines3/5

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

Usage is implied but not explicitly stated; no when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or exclude use cases.

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/dipseth/google_workspace_fastmcp2'

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