Skip to main content
Glama
kojott

mailmcp

by kojott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Read a message

get_message
Read-onlyIdempotent

Retrieve a single email's headers, sanitized text body, and attachment list by account and UID. Body is truncated to a configurable limit.

Instructions

Returns headers, sanitized text body and the attachment list of one message. Body is truncated to the configured limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesuid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned
folderNoFolder/label path. Defaults to All Mail on Gmail, INBOX elsewhere.
accountYesAccount id from list_accounts
max_charsNo
include_quotedNoKeep quoted replies (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.8.1
    • changedInput schema / properties / uid / description
      Previous value: -"uid from search_messages"New value: +"uid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned"
    • addedInput schema / properties / uid / maxLength
      Added value: +512
    • removedInput schema / properties / uid / maximum
      Removed value: -9007199254740991
    • addedInput schema / properties / uid / minLength
      Added value: +1
    • removedInput schema / properties / uid / minimum
      Removed value: -1
    • changedInput schema / properties / uid / type
      Previous value: -"integer"New value: +"string"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only and idempotent behavior, so the description's added notes about sanitized text and body truncation provide useful behavioral context beyond the annotations. It transparently discloses that the body may not be complete.

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

Conciseness5/5

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

Two tight sentences with no filler. The most important information—what is returned and the truncation caveat—is front-loaded and each sentence contributes meaning.

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

Completeness4/5

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

For a read-only single-message tool, the description plus schema and annotations cover essential invocation needs. The absence of an output schema is partially mitigated by specifying the return categories, though the exact format of headers and attachments is left implied.

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 coverage is high at 80% and most parameters are already described. The description adds general context about body truncation, which relates to max_chars, but it does not explicitly link the configured limit to the max_chars parameter. It adds modest value beyond the schema.

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

Purpose5/5

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

The description names a specific operation ('Returns headers, sanitized text body and the attachment list') on a specific resource ('one message'). It clearly distinguishes this from fetching a thread or an attachment, and the singular scope prevents confusion with list/search operations.

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?

The description does not state when to prefer this tool over siblings like get_thread, search_messages, or fetch. The uid parameter schema hints it comes from search_messages, but the description itself offers no explicit usage context or exclusions.

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

Deploy Server

Other Tools