Skip to main content
Glama
mail-mcp-server

mail-mcp-server

list_drafts

Lists drafts in a connected mailbox, showing each draft's ID, recipients, subject, and date so you can review unsent messages before editing or sending.

Instructions

The mailbox's drafts: id, recipients, subject, date.

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": {
      "mailbox": "<mailbox>"
    },
    "name": "list_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoDefault 25, at most 100
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it: no ordering, no statement of whether the default cap truncates results, no permission/auth requirements, and no indication of whether all drafts or only recent ones are returned. The only disclosure is which fields come back.

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

Conciseness3/5

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

It is a single front-loaded fragment with no wasted words, but it is terse to the point of under-specification rather than genuinely efficient — the brevity comes at the cost of the guidance an agent needs.

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?

With no annotations and no output schema, the description does at least enumerate returned fields, which partly compensates. But for a list operation with pagination behavior and a required mailbox parameter, missing scope, ordering, truncation and preconditions leave it materially incomplete.

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 100%, so mailbox and max are already fully documented, and the description adds no parameter-level meaning beyond that. The field enumeration describes output rather than inputs, leaving parameter semantics at the baseline.

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?

The phrase 'The mailbox's drafts' names the resource and the field list (id, recipients, subject, date) makes clear this is a listing/read of drafts, which separates it from create_draft, update_draft and delete_draft. It stops short of an explicit verb and never states scope, but an agent can infer the operation reliably.

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 when-to-use guidance at all — nothing about how this differs from search, get_message, get_thread or create_draft, and no note that a mailbox must be connected first. Usage is only implied by the tool name.

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