Skip to main content
Glama

Create Email Draft

create_draft

Creates a new email draft in the Drafts folder with recipients, subject, and body, optionally adding CC/BCC, choosing text or HTML, or acting on a shared mailbox.

Instructions

Create a new email draft in the Drafts folder

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCC recipients (comma-separated email addresses)
toYesRecipient email address(es), comma-separated for multiple
bccNoBCC recipients (comma-separated email addresses)
bodyYesEmail body content
mailboxNoEmail address of another mailbox to act on (delegated or shared), e.g. 'someone@example.com'. Omit for your own mailbox; required when this server signs in as an application. Only addresses this server is configured to allow will be accepted.
subjectYesEmail subject
content_typeNoBody content type: Text or HTML (default: Text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the result lands in the Drafts folder, implicitly signaling the message is not sent, but it says nothing about the delegated-mailbox auth constraint that the schema hints at or that send_draft is needed afterwards.

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?

A single front-loaded sentence with no redundant wording. It is efficient, though it is arguably too thin for a seven-parameter mutation tool.

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?

With no output schema, the description could usefully say what identifier is returned for later update_draft or send_draft calls, and it omits the unsent-draft lifecycle. The rich schema compensates for parameter detail, but the description leaves real gaps for a write operation with delegation semantics.

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%, including detailed mailbox delegation semantics, so the schema carries the parameter burden. The description adds no additional meaning about recipients, content_type, or mailbox beyond what the schema already states.

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 gives a specific verb and resource ("Create a new email draft") plus a destination ("Drafts folder"), so an agent knows exactly what artifact is produced. It does not, however, differentiate from close siblings such as create_reply_draft or create_forward_draft, which also create drafts.

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?

There is no guidance on when to use this tool versus create_reply_draft, create_reply_all_draft, or create_forward_draft, nor any mention of prerequisites. The agent must infer selection from the tool name alone.

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

Deploy Server

Other Tools