gmail

draft_email

Create a new email draft saved to the Drafts folder. Use this when composing an email to review or send later. The draft can be sent using send_draft. Plain text is automatically formatted with markdown. Optionally provide HTML for rich formatting.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	CC recipient email addresses
`to`	Yes	Recipient email addresses (e.g., ['user@example.com'])
`bcc`	No	BCC recipient email addresses
`subject`	Yes	Email subject line
`body_html`	No	Optional HTML version for rich formatting
`body_text`	Yes	Plain text email body. Supports markdown formatting

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`message`	Yes
`createdMessage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedFeb 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "createdMessage": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "labelIds": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "threadId": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "threadId"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "id",
+    "message",
+    "createdMessage"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations indicate this is a non-destructive write operation (readOnlyHint=false, destructiveHint=false). The description adds valuable behavioral context beyond annotations: it specifies that drafts are saved to the Drafts folder, plain text is automatically formatted with markdown, and HTML can be optionally provided for rich formatting. No contradictions with annotations.

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?

Three concise sentences with zero waste. First sentence states the core purpose, second provides usage guidelines and alternative tool, third explains formatting behavior. Every sentence earns its place by adding distinct value.

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

Completeness5/5

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

Given that this tool has annotations covering safety profile, 100% schema description coverage, and an output schema exists (so return values are documented elsewhere), the description provides complete contextual information. It covers purpose, usage guidelines, behavioral traits, and formatting behavior without needing to repeat structured data.

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 description coverage is 100%, so the schema already documents all 6 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions that plain text supports markdown formatting (implied by body_text's schema description) and HTML is optional for rich formatting (implied by body_html's optional nature). Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Create a new email draft saved to the Drafts folder') and distinguishes it from siblings like 'draft_reply' (which replies to existing emails) and 'send_draft' (which sends already-created drafts). It specifies the resource (email draft) and destination (Drafts folder).

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?

Explicitly states when to use this tool ('when composing an email to review or send later') and names an alternative tool for subsequent actions ('The draft can be sent using send_draft'). It also distinguishes from 'draft_reply' by not mentioning replying to existing emails.

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

All gmail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.