Skip to main content
Glama

imap_append_message

Append a raw RFC822 message to a specified mailbox, enabling you to store or import complete email content directly via IMAP.

Instructions

Append a raw RFC822 message to a mailbox

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": {
      "mailbox": "<mailbox>",
      "raw_message": "<raw_message>"
    },
    "name": "imap_append_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesTarget mailbox name
account_idNoAccount identifier (defaults to `"default"`)default
raw_messageYesRaw RFC822 message content (as UTF-8 string)

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

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, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered without help from the description. The description adds no further behavioral context — no warning that non-idempotent appends may duplicate messages on retry, no note on resulting flags (e.g. \Seen or \Draft), and no mention of quota or permission failures.

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 front-loaded sentence with zero wasted words, which makes the purpose immediately scannable. Its brevity is efficient rather than padded, though it borders on under-specification given the tool's write behavior.

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?

An output schema exists and annotations cover the mutation profile, so the agent is not missing return-value or safety information. What remains absent is guidance on choosing this tool over the many sibling message-manipulation tools and on the duplicate-append risk implied by idempotentHint=false, making it adequate but not complete.

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% with only 3 parameters, so the schema already carries mailbox, account_id, and raw_message semantics including the UTF-8 string encoding. The description's 'raw RFC822' phrasing merely echoes the schema, adding no format or size constraints beyond it. 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 ('Append') and resource ('raw RFC822 message to a mailbox'), so the operation is unambiguous. It does not, however, distinguish itself from sibling write paths such as imap_copy_message (copying an existing message) or draft_create (creating a draft), leaving the agent to infer when appending raw content is the right choice.

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 or when-not-to-use guidance at all. Nothing tells the agent why it would append a raw message rather than call imap_copy_message, imap_move_message, or draft_create, nor that the target mailbox may be a drafts folder.

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