Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_draft_list

List email drafts for a specified account, with pagination via limit and offset to review or manage saved drafts.

Instructions

List email drafts

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": "email_draft_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. 'List' weakly implies a non-mutating read, but there is no mention of pagination defaults, maximum limit values, sort order, or what fields each draft contains. For a paginated list endpoint with zero annotation coverage, this is a substantial gap.

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?

At three words the text is maximally front-loaded and contains no filler, so it cannot be accused of verbosity. But this is under-specification rather than conciseness; the brevity leaves no room for the scoping and pagination facts an agent needs.

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

Completeness1/5

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

The tool has three parameters, one required, no annotations, and no output schema, so the description is the only source of context and it supplies none. An agent cannot determine default page size, ordering, or the meaning of accountId from this definition. This is inadequate for the tool's actual complexity.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description compensates for none of it. It never explains what accountId identifies, whether limit/offset are required or optional, what the default page size is, or any upper bound on limit. With the schema silent and the description silent, an agent has no semantic anchor for any parameter.

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

Purpose3/5

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

The description names a verb ('List') and a resource ('email drafts'), so the intent is discernible. However, it is essentially a restatement of the tool name 'email_draft_list' and does not distinguish this from siblings like email_search or email_get_thread that could also surface draft content. It is clear but adds no specificity beyond the identifier.

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: no statement of when to prefer this over email_search, no mention that it returns only drafts (not sent mail), and no prerequisites such as needing an authenticated account. The agent must infer usage entirely from the name.

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