Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_send

Sends a new email from a configured account with recipients, subject, body, optional CC/BCC, attachments, and signature support.

Instructions

Send a new email

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

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
subjectYes
accountIdYes
signatureNoAdd the account's signature (default true). Gmail: the signature of the send-as address the mail goes out from, read from Gmail's settings, in Gmail's own markup above any quoted history; a body that already holds one is left alone. Outlook.com, iCloud and IMAP have no signature a client can read, so nothing is added there. The result's `signature` field says what happened
attachmentsNoFiles to attach, at most 100. Total size is capped at 25 MB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. "Send" implies immediate, irreversible dispatch, but nothing states whether the message is queued, whether sending requires a verified accountId, what happens on partial failure with 500 recipients, or what the result contains. Only the implicit send-semantics come through.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but it is terse to the point of under-specification rather than efficiently concise. There is no waste, but there is also almost no content for the space it occupies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 8 parameters, nested objects, no annotations, and no output schema, four words are nowhere near sufficient. Critical facts such as the 25 MB/100-attachment cap on sends, recipient limits, and the irreversible nature of the send are absent from the description.

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

Parameters1/5

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

Schema description coverage is only 25% across 8 parameters including nested to/cc/bcc/attachments objects, and the description adds no parameter meaning whatsoever. Recipient limits, body text-vs-html precedence, and accountId semantics are left entirely to the schema, which itself documents only signature and attachments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Send a new email" gives a specific verb (send) and resource (email), so the basic action is clear. But it does nothing to distinguish this from siblings like email_draft_create, email_reply, or email_forward, which all produce email content. An agent must infer that this sends immediately rather than saving a draft.

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 when-to-use guidance at all: no mention of when to choose this over email_draft_create, email_reply, or email_forward, and no prerequisites such as needing a configured account. Usage must be inferred entirely from the tool name and sibling names.

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