Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_get

Retrieve a single email by ID from a specified account, optionally providing the source folder for IMAP or iCloud when the message is outside INBOX.

Instructions

Get a single email by ID

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>",
      "emailId": "<emailId>"
    },
    "name": "email_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether reading marks the email as read, what happens when the ID is missing or the email was deleted, or whether the full body is returned. The one behavioral hint in the definition (folder requirement for IMAP/iCloud) lives in the schema, not the description.

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, which is good, but the brevity reads as under-specification rather than economy. There is room for a short clause on folder fallback without bloating it.

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

Completeness2/5

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

For a 3-parameter retrieval tool with no annotations and no output schema, the description should at minimum state what comes back and how the IMAP/iCloud folder case behaves. Neither is present, so an agent must open the schema and guess at runtime behavior.

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

Parameters2/5

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

Schema coverage is only 33% — only sourceFolder is documented — so the description is expected to compensate and does not. It says nothing about what accountId identifies or when emailId might need a folder qualifier, leaving two of three parameters unexplained in both places.

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?

"Get a single email by ID" gives a specific verb (get), a specific resource (a single email), and the lookup key (ID), which cleanly separates it from email_search and email_get_thread. It stops short of naming any sibling or stating scope limits, so it is clear but not maximally differentiating.

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, no mention of when to prefer email_search or email_get_thread instead, and no prerequisites such as needing a valid accountId first. The agent must infer all routing from the tool name alone.

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