Skip to main content
Glama
Sign In

GhosterMail

by com.ghostermail
OverviewDiscussionsAdmin

List messages

list_messages
Read-onlyIdempotent

Lists messages of a mailbox folder, newest first (20 per page). Returns message ids, senders, subjects and short snippets. Use 'read_message' to get the full message.

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": {
      "accountId": "<accountId>"
    },
    "name": "list_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoOptional filter: sender address or name contains this text.
textNoOptional filter: message contains this text.
folderNoFolder name: INBOX, SENT, DRAFTS, TRASH, SPAM, DELAYED SEND or a custom folder. Default: INBOX.INBOX
subjectNoOptional filter: subject contains this text.
accountIdYesMailbox id (see 'list_accounts').
beforeMessageIdNoFor the next page: pass 'nextBeforeMessageId' from the previous result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral details beyond annotations: results are newest first, paginated at 20 per page, and return only ids, senders, subjects, and short snippets rather than full bodies.

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?

The description is two tight sentences with no wasted wording. It front-loads the primary purpose, then adds pagination and return behavior, and closes with a clear sibling redirect.

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 read-only listing tool with rich annotations, complete schema coverage, and no output schema, the description provides everything an agent needs: scope, ordering, page size, returned fields, and when to use the sibling read_message instead.

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 six parameters are already documented in the input schema. The description does not add meaningful parameter semantics beyond what the schema provides, such as clarifying filter combinations or pagination behavior in more detail.

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 states a specific verb and resource: lists messages in a mailbox folder. It also names the sibling tool read_message and clarifies that this tool only returns summaries, which immediately distinguishes it from the full-message reader.

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?

The description explicitly says to use 'read_message' to get the full message, giving clear guidance on the main alternative. It does not mention other siblings like wait_for_message, but the core usage decision for listing versus reading is well covered.

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

All GhosterMail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources