Skip to main content
Glama
Sign In
your-mail-mcp

your-mail-mcp

by wildsurfer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

text

Read-only

Retrieve the plain-text body of a single email, converting HTML to text and returning byte-limited chunks so long messages can be read in full.

Instructions

Return the plain-text body of one message, converting HTML.

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": {
      "id": "<id>"
    },
    "name": "text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets.
limitNoHow many bytes of text to return at most. Defaults to 65536, which is also the ceiling.
offsetNoByte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start.
include_excludedNoSet true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / id / description
      Added value: +"Message-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets."
    • addedInput schema / properties / include_excluded / description
      Added value: +"Set true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile."
    • addedInput schema / properties / limit / description
      Added value: +"How many bytes of text to return at most. Defaults to 65536, which is also the ceiling."
    • addedInput schema / properties / offset / description
      Added value: +"Byte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start."
  2. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds one behavioral fact – HTML is converted to plain text – but says nothing about truncation, hostility of junk/trash, or what the conversion loses, all of which the schema, not the description, carries.

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?

A single front-loaded sentence with zero filler; every word (plain-text, body, one message, converting HTML) carries information.

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?

With four fully documented parameters, an explicit required id, and annotations covering the safety profile, the definition is nearly complete; the return value is captured by 'plain-text body'. Only pagination/truncation behavior is left entirely to the schema.

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 id, limit, offset, and include_excluded are fully documented in the schema; the description adds no syntax, format, or interaction detail beyond it. Baseline 3 is correct when the schema does all the work.

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 (return) and resource (plain-text body of one message) plus the transformation (converting HTML), which separates it from siblings like attachment or thread. It does not explicitly name a sibling it is not, which keeps it just under a 5.

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 statement of when to use this tool versus show, thread, or attachment, nor any prerequisites (e.g., message must be reachable). The single sentence describes only what happens, leaving selection to inference from the name.

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