Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_draft_update

Update an existing email draft's recipients, subject, and body in place while keeping reply drafts in their thread. Use the returned draft ID, since IMAP providers replace the draft.

Instructions

Update an existing email draft in place (to/subject/body). A reply draft stays in its thread. On Gmail and Outlook the draft id is unchanged. On iCloud/generic IMAP there is no in-place update (the old draft is deleted and a new one appended), so the returned id is a NEW id and the old one no longer resolves; always use the id this call returns, not the one you passed in.

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": {
      "accountId": "<accountId>",
      "draftId": "<draftId>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "email_draft_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
draftIdYes
subjectYes
accountIdYes
signatureNoAdd the account's signature (default true), as on email_draft_create. The body given here replaces the draft's body, so the signature is added to it once; a body that already holds one (passed back from the draft) is left alone, so repeated updates never stack a second one
attachmentsNoFiles to attach. When given, they replace the draft's current attachments; an empty list removes them all. When omitted, the draft keeps the files it has.
sourceFolderNoSource folder (required for IMAP/iCloud when the draft is not in the default Drafts folder)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well on the highest-risk details: reply drafts stay threaded, Gmail/Outlook preserve the draft id, and iCloud/generic IMAP deletes the old draft and appends a new one so the returned id must be used. It does not cover permissions, failure modes, or optional attachment/signature replacement behavior.

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 front-loaded with the purpose and spends its remaining words on the important platform-specific id caveat. The second sentence is dense but each clause carries operational meaning, with no obvious filler.

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?

For a mutation tool with no annotations and no output schema, the description covers the critical cross-provider id behavior and thread semantics that an agent must know. It leaves some gaps around accountId and optional attachment/signature handling, though several of those optionals have schema descriptions.

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 only 38%, so the description would ideally compensate more. It names to/subject/body and explains the draftId return-value caveat, but it does not explain accountId, the shape of to/body, or the semantics of optional parameters like signature, attachments, and sourceFolder beyond what the schema already documents.

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 opens with a specific verb and resource: 'Update an existing email draft in place' and names to/subject/body as the updated fields. It implicitly distinguishes update from create by requiring an existing draft, but it does not explicitly name a sibling tool such as email_draft_create as the alternative.

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?

The use case is implied: modifying an existing draft rather than creating a new one. However, the description gives no explicit when-to-use guidance versus email_draft_create, email_reply, or other draft-related siblings, and it states no prerequisites or exclusions.

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