Skip to main content
Glama
owlpost

owlpost

save_draft_email

Compose an email and save it to the account's Drafts folder for review before sending; each call creates a new draft you can edit and send from your mail client.

Instructions

Compose an email and save it to the account's Drafts folder without sending it.

The message is appended to the special-use Drafts folder with the \Draft flag, so the user can review, edit and send it from their own mail client. Use this instead of send_email whenever the user wants to check a message first. Each call creates a new draft.

Args: account: Account name from list_accounts. to: Recipient email addresses. subject: Subject line. body: Plain-text body. cc: Cc recipient addresses. bcc: Bcc recipient addresses. html: Optional HTML alternative to the plain-text body. attachments: Local file paths to attach. in_reply_to: Message-ID this draft replies to, for threading. references: Message-IDs of earlier messages in the thread.

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": {
      "account": "<account>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "save_draft_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
htmlNo
accountYes
subjectYes
referencesNo
attachmentsNo
in_reply_toNo

Output Schema

NameRequiredDescriptionDefault
ccYes
toYes
bccYes
fromYes
subjectYes
message_idYes
size_bytesYes
saved_to_folderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bcc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Bcc",
      +      "type": "array"
      +    },
      +    "cc": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "Cc",
      +      "type": "array"
      +    },
      +    "from": {
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "message_id": {
      +      "title": "Message Id",
      +      "type": "string"
      +    },
      +    "saved_to_folder": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Saved To Folder"
      +    },
      +    "size_bytes": {
      +      "title": "Size Bytes",
      +      "type": "integer"
      +    },
      +    "subject": {
      +      "title": "Subject",
      +      "type": "string"
      +    },
      +    "to": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "title": "To",
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "from",
      +    "to",
      +    "cc",
      +    "bcc",
      +    "subject",
      +    "saved_to_folder",
      +    "size_bytes"
      +  ],
      +  "title": "DraftResult",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (which already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the actual mechanism: appended to the special-use Drafts folder with the \Draft flag, and 'Each call creates a new draft', which reinforces non-idempotency concretely. It does not mention failure modes such as invalid account or missing attachment paths.

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?

Front-loaded with the core action and the send_email contrast before the Args block, and no filler sentences. The Args block is somewhat verbose at 10 lines but each maps to a distinct parameter.

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?

For a 10-parameter mutation whose return values are already covered by an output schema, the description supplies folder/flag semantics, threading guidance for in_reply_to and references, and per-parameter meaning. Nothing an agent needs to construct a correct call is missing.

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 description coverage is 0%, so the description carries the full param burden; its Args block documents all 10 parameters and adds real meaning where the schema has only titles — 'Message-ID this draft replies to, for threading', 'Message-IDs of earlier messages in the thread', 'Local file paths to attach', and the cross-reference 'Account name from list_accounts'. A few entries (subject, body) are near-restatements, keeping it short of 5.

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?

States the specific verb+resource ('Compose an email and save it to the account's Drafts folder without sending it') and immediately contrasts with send_email, so an agent can separate it from the closest sibling 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 Guidelines4/5

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

Explicitly says 'Use this instead of send_email whenever the user wants to check a message first', which is a clear when-to-use rule with a named alternative. It does not address when to prefer reply_email/forward_email versus using in_reply_to/references here, leaving one sibling relationship to inference.

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