Skip to main content
Glama

Send Email Draft

send_draft
Destructive

Sends an existing email draft using its message ID, optionally from a specified shared or delegated mailbox.

Instructions

Send an existing email draft

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": {
      "message_id": "<message_id>"
    },
    "name": "send_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
message_idYesThe draft message ID to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the bar is lower, but the description adds nothing beyond them: it does not say the send is irreversible, that the draft is consumed/converted on success, or what failure leaves behind. For an irreversible send action, no behavioral context beyond the annotation flags is provided.

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?

Five words, front-loaded with the verb and free of filler. It is terse to the point of under-specification, but no sentence is wasted.

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?

The tool is simple (one required parameter) and annotations carry the destructive profile, and the schema carries the mailbox nuance. What remains missing is the consequence of the call — that sending is final and the draft leaves the drafts folder — which matters for an irreversible operation.

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%, and the mailbox parameter's delegated/shared semantics plus allow-list constraint are fully documented in the schema. The description adds no meaning to message_id or mailbox, so the baseline 3 applies.

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?

States a specific verb (send) and resource (an existing email draft), which implicitly distinguishes it from create_draft and from send_message/send_reply that compose new mail. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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?

The phrase 'existing email draft' implies a prior create_draft step, but there is no explicit when-to-use, no exclusions, and no mention of send_message or send_reply as alternatives. An agent must infer the whole decision from the word 'draft'.

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