Skip to main content
Glama

imap_get_message_raw

Read-onlyIdempotent

Fetch a raw RFC822 email message by stable message ID, capped at a configurable byte limit to inspect original source without oversized responses.

Instructions

Get bounded RFC822 source

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": {
      "message_id": "<message_id>"
    },
    "name": "imap_get_message_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_bytesNoMaximum message bytes to return (1024..1000000, default 200000)
account_idNoAccount identifier (defaults to `"default"`)default
message_idYesStable message identifier

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.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The word "bounded" hints that the returned source is truncated at max_bytes, but the description never states whether truncation is signalled, whether bytes are decoded, or that fetching large messages is capped by default at 200KB.

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 four-word phrase with no waste and the key noun front-loaded. It is compact, though its brevity borders on under-specification rather than true conciseness.

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?

An output schema exists, so return values need not be explained, but the definition still omits what makes this tool distinct from the parsed-message sibling and how raw output behaves. For a fetch tool with a payload-bounding parameter, that is a meaningful gap.

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%, so all three parameters (message_id, account_id, max_bytes) are documented in the schema itself. The description adds no meaning beyond that, which is the baseline expectation when the schema is complete.

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?

"Get bounded RFC822 source" names a verb and a resource, but the resource is jargon (RFC822 raw source) and "bounded" is unexplained. It does not distinguish this from the sibling imap_get_message, which an agent would naturally confuse with a raw-fetch tool.

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 when-to-use guidance is given at all, and no condition distinguishes it from imap_get_message or imap_get_attachment. The agent must infer that this fetches unparsed bytes rather than a parsed message.

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