Skip to main content
Glama
owlpost

owlpost

read_email

Read-onlyIdempotent

Read a specific email by account, folder, and UID without marking it read; retrieve decoded headers, plain-text body, attachment list, and threading details.

Instructions

Read one message: decoded headers, body and attachment list, without marking it read.

By default only the plain-text body is returned, truncated at 50,000 characters to fit MCP result limits; the untruncated sizes are always reported as text_full_length and html_full_length. Attachments are listed with a 1-based part index for save_attachment. Threading headers (message_id, in_reply_to, references) are included.

Args: account: Account name from list_accounts. folder: Folder containing the message. uid: Message UID from search_messages. include_html: Also return the HTML body (default false). HTML mail can be very large. include_text: Return the plain-text body (default true). body_max_chars: Truncate each body to this many characters (default 50000).

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": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>"
    },
    "name": "read_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderYes
accountYes
include_htmlNo
include_textNo
body_max_charsNo

Output Schema

NameRequiredDescriptionDefault
ccYes
toYes
bccYes
uidYes
dateYes
fromYes
htmlYes
seenYes
textYes
flagsYes
folderYes
flaggedYes
subjectYes
date_isoYes
message_idYes
referencesYes
attachmentsYes
in_reply_toYes
html_full_lengthYes
text_full_lengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedOutput schema / $defs
      Added value: +{
      +  "Address": {
      +    "properties": {
      +      "email": {
      +        "title": "Email",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "email"
      +    ],
      +    "title": "Address",
      +    "type": "object"
      +  },
      +  "Attachment": {
      +    "properties": {
      +      "content_id": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Content Id"
      +      },
      +      "filename": {
      +        "title": "Filename",
      +        "type": "string"
      +      },
      +      "mime": {
      +        "title": "Mime",
      +        "type": "string"
      +      },
      +      "part": {
      +        "title": "Part",
      +        "type": "integer"
      +      },
      +      "size": {
      +        "title": "Size",
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "part",
      +      "filename",
      +      "mime",
      +      "size",
      +      "content_id"
      +    ],
      +    "title": "Attachment",
      +    "type": "object"
      +  }
      +}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
      +  "attachments": {
      +    "items": {
      +      "$ref": "#/$defs/Attachment"
      +    },
      +    "title": "Attachments",
      +    "type": "array"
      +  },
      +  "bcc": {
      +    "items": {
      +      "$ref": "#/$defs/Address"
      +    },
      +    "title": "Bcc",
      +    "type": "array"
      +  },
      +  "cc": {
      +    "items": {
      +      "$ref": "#/$defs/Address"
      +    },
      +    "title": "Cc",
      +    "type": "array"
      +  },
      +  "date": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "Date"
      +  },
      +  "date_iso": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "Date Iso"
      +  },
      +  "flagged": {
      +    "title": "Flagged",
      +    "type": "boolean"
      +  },
      +  "flags": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "title": "Flags",
      +    "type": "array"
      +  },
      +  "folder": {
      +    "title": "Folder",
      +    "type": "string"
      +  },
      +  "from": {
      +    "items": {
      +      "$ref": "#/$defs/Address"
      +    },
      +    "title": "From",
      +    "type": "array"
      +  },
      +  "html": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "Html"
      +  },
      +  "html_full_length": {
      +    "title": "Html Full Length",
      +    "type": "integer"
      +  },
      +  "in_reply_to": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "In Reply To"
      +  },
      +  "message_id": {
      +    "title": "Message Id",
      +    "type": "string"
      +  },
      +  "references": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "title": "References",
      +    "type": "array"
      +  },
      +  "seen": {
      +    "title": "Seen",
      +    "type": "boolean"
      +  },
      +  "subject": {
      +    "title": "Subject",
      +    "type": "string"
      +  },
      +  "text": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "Text"
      +  },
      +  "text_full_length": {
      +    "title": "Text Full Length",
      +    "type": "integer"
      +  },
      +  "to": {
      +    "items": {
      +      "$ref": "#/$defs/Address"
      +    },
      +    "title": "To",
      +    "type": "array"
      +  },
      +  "uid": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "title": "Uid"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[
      +  "uid",
      +  "folder",
      +  "message_id",
      +  "in_reply_to",
      +  "references",
      +  "subject",
      +  "from",
      +  "to",
      +  "cc",
      +  "bcc",
      +  "date",
      +  "date_iso",
      +  "flags",
      +  "seen",
      +  "flagged",
      +  "text",
      +  "html",
      +  "text_full_length",
      +  "html_full_length",
      +  "attachments"
      +]
    • changedOutput schema / title
      Previous value: -"read_emailDictOutput"New value: +"Message"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description goes well beyond them: default body selection, 50,000-character truncation rationale (MCP result limits), the text_full_length/html_full_length size reporting, 1-based attachment part indices for save_attachment, and inclusion of threading headers. These are exactly the behaviors an agent needs to plan around and cannot get from the annotations.

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?

The core behavior is front-loaded in the first sentence and the truncation caveat follows immediately; nothing is padded. The docstring-style 'Args:' block is slightly mechanical with wrapped lines, but given zero schema coverage that enumeration is necessary rather than wasteful.

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

Completeness5/5

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

For a six-parameter read tool with an output schema, the definition covers the side-effect question, size/truncation limits, and the cross-tool linkage for attachments. Return-value detail is correctly delegated to the existing output schema, so nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: every one of the six parameters is explained, including defaults (include_html=false, include_text=true, body_max_chars=50000), provenance of required identifiers, and the warning that HTML mail can be very large. This is meaning the schema alone does not convey.

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?

States a specific verb and resource ('Read one message') and enumerates exactly what comes back: decoded headers, body, attachment list. The phrase 'without marking it read' immediately separates it from mark_read, and the mention of save_attachment/list_accounts/search_messages anchors it against siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: it points to list_accounts, search_messages and save_attachment as the sources for its arguments, and the 'without marking it read' clause implies mark_read is the tool for that side effect. There is no explicit statement about when to prefer get_conversation over this tool for whole-thread reads, which keeps it from a 5.

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