Skip to main content
Glama
chandshy

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Scheduled Emails

list_scheduled_emails
Read-only

View all scheduled emails, including in-flight deliveries with unknown outcomes. Sorted by send time ascending to help track pending messages.

Instructions

List all scheduled emails, including in-flight and outcome-unknown deliveries. Sorted by scheduledAt ascending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
scheduledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.2.0
    • addedOutput schema / properties / scheduled / items / properties / status / description
      Added value: +"outcome_unknown means SMTP was interrupted after dispatch; inspect Sent mail before retrying manually"
    • changedOutput schema / properties / scheduled / items / properties / status / enum
      Previous value: -[
-  "pending",
-  "sent",
-  "failed",
-  "cancelled"
-]New value: +[
+  "pending",
+  "sending",
+  "sent",
+  "failed",
+  "cancelled",
+  "outcome_unknown"
+]
  2. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  3. First observedv3.0.77

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description adds valuable behavioral context by specifying that it includes 'in-flight and outcome-unknown deliveries' and that results are sorted by 'scheduledAt ascending'. No contradictions.

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 concise sentences: the first states the action and scope, the second adds sorting. No unnecessary words or redundancy.

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?

Given the presence of an output schema and no additional parameters, the description covers the tool's functionality well. It could mention pagination or limits, but for a simple listing tool it is adequate.

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?

The schema has 100% coverage for the single parameter, with a detailed description. The tool description does not add extra parameter information, so it falls back to baseline 3.

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 clearly states the verb 'List', the resource 'scheduled emails', and specifies the scope 'including in-flight and outcome-unknown deliveries'. It also adds sorting order, making the purpose unambiguous and distinct from sibling tools like 'cancel_scheduled_email'.

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

Usage Guidelines3/5

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

The description implies usage for viewing scheduled emails but does not explicitly state when to use this tool versus alternatives like 'cancel_scheduled_email' or when not to use it. No prerequisites or context are given.

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