Skip to main content
Glama

MCP Emails

Scheduled Send

schedule
Destructive

Queue a message from one inbox for delivery at a future time, or cancel one that is queued. Use email_compose to send now; use this only when the user names a later time. send_at is an ISO 8601 timestamp WITH a timezone offset ("2026-06-02T09:00:00+02:00" or a trailing Z), in the future; the server dispatches within about 60 seconds of it, so it is not for second-precise timing. Recipients and body are validated at create time and an invalid message is never queued. Attachments here are inline base64 { filename, mime_type, data } only, 10 MB total; the { source_message_id, attachment_index } reference form belongs to email_compose. Only a send still 'pending' can be cancelled; use schedule_list to see what is queued and to get the id that 'cancel' takes. Every action needs the schedule:email scope. A cancel result is your own queued data, not mailbox content, so it carries no untrusted_content flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCc addresses.
idNoScheduled send UUID from a create or list call.
toNoRecipient addresses.
bccNoBcc addresses.
bodyNoPlain-text body. Sent as multipart/alternative when html_body is given too.
inboxNoInbox email address, an alternative to inbox_id.
actionYesOperation to run. create = queue to, subject and body for send_at; cancel = a pending send by `id`.
send_atNoSend time, in the future and carrying a timezone (e.g. '2026-06-01T09:00:00+02:00'). The dispatcher runs every minute, so delivery can be up to 60s late.
subjectNoSubject line. The limit is the 998-octet header line, so a non-ASCII subject (RFC 2047 encoded) must be shorter in characters.
inbox_idNoInbox UUID from inbox_list. Optional when the key has one inbox; pass this or `inbox`, not both — a pair naming different mailboxes is refused.
reply_toNoReply-To address.
html_bodyNoOptional HTML body.
attachmentsNoFile attachments, 10 MB total. Inline base64 only here — the { source_message_id, attachment_index } reference form is email_compose's, not this tool's.
idempotency_keyNoReuse only when retrying the identical request within 24 hours; the retry is collapsed, not repeated. Reuse with different arguments is rejected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoServer notes about how this call was handled — for example an argument that was not applied because the selected action does not accept it. Written by MCP Emails, not taken from any message, and absent when there is nothing to report.
totalNo
inbox_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / inbox_id / description
      Previous value: -"Inbox UUID from inbox_list. Optional when the key has one inbox; pass this or `inbox`, not both."New value: +"Inbox UUID from inbox_list. Optional when the key has one inbox; pass this or `inbox`, not both — a pair naming different mailboxes is refused."
  2. Changed22 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which operation to perform. Determines which other arguments are used."New value: +"Operation to run. create = queue to, subject and body for send_at; cancel = a pending send by `id`."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "create",
      -  "list",
      -  "cancel"
      -]New value: +[
      +  "create",
      +  "cancel"
      +]
    • changedInput schema / properties / attachments / description
      Previous value: -"Optional file attachments. Maximum 20 items. Total size must not exceed 10 MB."New value: +"File attachments, 10 MB total. Inline base64 only here — the { source_message_id, attachment_index } reference form is email_compose's, not this tool's."
    • changedInput schema / properties / attachments / items / properties / data / description
      Previous value: -"Base64-encoded attachment content."New value: +"Base64-encoded content."
    • changedInput schema / properties / attachments / items / properties / filename / description
      Previous value: -"Attachment filename."New value: +"Filename the recipient sees."
    • changedInput schema / properties / attachments / items / properties / mime_type / description
      Previous value: -"MIME type of the attachment."New value: +"MIME type."
    • changedInput schema / properties / bcc / description
      Previous value: -"List of BCC recipient email addresses. Optional."New value: +"Bcc addresses."
    • changedInput schema / properties / body / description
      Previous value: -"Email body as plain text. If html_body is also provided, the message is sent as multipart/alternative."New value: +"Plain-text body. Sent as multipart/alternative when html_body is given too."
    • changedInput schema / properties / cc / description
      Previous value: -"List of CC recipient email addresses. Optional."New value: +"Cc addresses."
    • changedInput schema / properties / html_body / description
      Previous value: -"Optional HTML version of the email body."New value: +"Optional HTML body."
    • changedInput schema / properties / id / description
      Previous value: -"UUID of the scheduled send to cancel, as returned by schedule_create and schedule_list. Alias of scheduled_send_id."New value: +"Scheduled send UUID from a create or list call."
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Reuse only when retrying the identical request within 24 hours; the retry is collapsed, not repeated. Reuse with different arguments is rejected.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / inbox / description
      Previous value: -"Email address of the inbox to use, as a friendly alternative to inbox_id. Optional; ignored if inbox_id is given."New value: +"Inbox email address, an alternative to inbox_id."
    • changedInput schema / properties / inbox_id / description
      Previous value: -"UUID of the inbox to use. Optional when the API key has access to exactly one inbox (it is auto-selected). Alternatively pass `inbox` with an email address. If you don't know the inbox_id and several are accessible, just omit it — the response then lists every inbox with its inbox_id so you can retry (calling inbox_list does the same)."New value: +"Inbox UUID from inbox_list. Optional when the key has one inbox; pass this or `inbox`, not both."
    • removedInput schema / properties / limit
      Removed value: -{
      -  "default": 20,
      -  "description": "Maximum number of results to return. Defaults to 20.",
      -  "maximum": 100,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • changedInput schema / properties / reply_to / description
      Previous value: -"Optional Reply-To header address."New value: +"Reply-To address."
    • removedInput schema / properties / scheduled_send_id
      Removed value: -{
      -  "description": "UUID of the scheduled send to cancel. Alias of `id` — provide either field.",
      -  "format": "uuid",
      -  "type": "string"
      -}
    • changedInput schema / properties / send_at / description
      Previous value: -"ISO 8601 datetime string (with timezone) at which the message should be sent. Must be in the future. Example: '2026-06-01T09:00:00Z' or '2026-06-01T09:00:00+02:00'. The dispatcher runs every minute so the actual send time may be up to 60 seconds after send_at."New value: +"Send time, in the future and carrying a timezone (e.g. '2026-06-01T09:00:00+02:00'). The dispatcher runs every minute, so delivery can be up to 60s late."
    • changedInput schema / properties / subject / description
      Previous value: -"Email subject line. Must be non-empty. Maximum 998 characters."New value: +"Subject line. The limit is the 998-octet header line, so a non-ASCII subject (RFC 2047 encoded) must be shorter in characters."
    • changedInput schema / properties / subject / maxLength
      Previous value: -998New value: +989
    • changedInput schema / properties / to / description
      Previous value: -"List of recipient email addresses. Each must be a valid RFC 5322 address. Maximum 50 recipients."New value: +"Recipient addresses."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "inbox_id": {
      +      "type": "string"
      +    },
      +    "notes": {
      +      "description": "Server notes about how this call was handled — for example an argument that was not applied because the selected action does not accept it. Written by MCP Emails, not taken from any message, and absent when there is nothing to report.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Even though annotations indicate destructiveHint and openWorldHint, the description adds substantial behavioral context: validation happens at create time so invalid messages are never queued, dispatch is approximate within 60 seconds, only pending sends can be cancelled, the schedule:email scope is required, and cancel results carry no untrusted_content flag. This goes well beyond the annotations and schema.

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 dense and front-loaded with the core purpose and routing guidance before details. It is long, and some content repeats what the schema already states, but every sentence carries operational value for a tool with 14 parameters and two actions.

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?

The description covers when to use, when not to use, parameter constraints, cancellation flow, attachment rules, auth requirements, validation behavior, and the untrusted_content characteristic of results. With an output schema present, nothing an agent needs to invoke this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaningful semantics: send_at must be a future time with timezone offset, delivery tolerance is about 60 seconds, attachments are inline base64 only and the reference form belongs to email_compose, and inbox_id/inbox cannot both name different mailboxes. These are exactly the details an agent needs to avoid invalid calls.

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 opens with a specific verb and resource: queue a message from one inbox for future delivery, or cancel one already queued. It also explicitly distinguishes itself from email_compose (send now) and schedule_list, so an agent can pick it from siblings without opening schemas.

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?

The description says exactly when to use this tool ('only when the user names a later time') and when not to ('Use email_compose to send now'), and points to schedule_list for discovering queued sends and obtaining cancel ids. It also clarifies that only pending sends can be cancelled and states the required scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.