Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_get_attachment

Retrieve an email attachment by account, email, and attachment ID, returning base64-encoded data for download or processing. Include the source folder for IMAP/iCloud messages outside INBOX.

Instructions

Get an email attachment by ID, returns base64 encoded data

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>",
      "attachmentId": "<attachmentId>"
    },
    "name": "email_get_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
attachmentIdYes
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.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavioral trait — the payload comes back base64 encoded — but says nothing about failure modes (missing attachment), size limits, or the folder-scoped lookup requirement for IMAP accounts.

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?

A single efficient sentence with the core action front-loaded and the return format appended. Nothing is wasted, though the brevity borders on under-specification rather than tight editing.

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 four-parameter tool with no annotations, no output schema, and mostly undocumented parameters, the description is too thin — it never explains the multi-identifier requirement or the conditional sourceFolder behavior that the schema itself flags as needed for IMAP/iCloud.

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 description coverage is only 25%: sourceFolder is the sole documented parameter, while accountId, emailId and attachmentId are bare strings. The description's 'by ID' hints that identifiers are required but adds no meaning about which ID, format, or how they are obtained.

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 and resource ('Get an email attachment by ID') and adds the return encoding. It does not distinguish itself from the close sibling email_save_attachment or explain how it relates to email_get, so differentiation is left to the agent.

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?

No guidance on when to use this rather than email_save_attachment or email_get, and no prerequisites stated (e.g., that account, email and attachment identifiers must all be resolved first). Usage must be inferred entirely from the name.

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