Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_messages_list

Retrieve summaries of messages from a Mailosaur server, with filtering by received date, pagination, and direction.

Instructions

List message summaries for a server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesMailosaur server ID.
optionsNo

Implementation Reference

  • The tool handler for 'mailosaur_messages_list'. Calls mailosaur.messages.list(server, toMessageListOptions(options)) and returns the result.
    server.tool(
      "mailosaur_messages_list",
      "List message summaries for a server.",
      {
        server: z.string().describe("Mailosaur server ID."),
        options: MessageListOptionsSchema.optional()
      },
      async ({ server, options }) => {
        const result = await mailosaur.messages.list(server, toMessageListOptions(options));
        return response(result);
      }
    );
  • Schema definition for MessageListOptions, used as the 'options' parameter of mailosaur_messages_list.
    const MessageListOptionsSchema = z.object({
      receivedAfter: z.string().datetime().optional(),
      page: z.number().int().min(0).optional(),
      itemsPerPage: z.number().int().min(1).max(1000).optional(),
      dir: z.enum(["Sent", "Received"]).optional()
    });
  • src/index.ts:136-147 (registration)
    Registration of the tool via server.tool() with name 'mailosaur_messages_list', description, schema, and handler.
    server.tool(
      "mailosaur_messages_list",
      "List message summaries for a server.",
      {
        server: z.string().describe("Mailosaur server ID."),
        options: MessageListOptionsSchema.optional()
      },
      async ({ server, options }) => {
        const result = await mailosaur.messages.list(server, toMessageListOptions(options));
        return response(result);
      }
    );
  • Helper function toMessageListOptions that converts the Zod schema options to the Mailosaur SDK's MessageListOptions type, including date parsing.
    function toMessageListOptions(options: z.infer<typeof MessageListOptionsSchema> | undefined): MessageListOptions | undefined {
      return parseDateOptions(options) as MessageListOptions | undefined;
    }
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only says 'list summaries' but omits pagination behavior, read-only nature, or output format.

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

Conciseness4/5

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

Single sentence, front-loaded with key information. Could be expanded slightly for clarity without being wasteful.

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?

Given no output schema, no annotations, and several sibling tools, description is too brief. It doesn't explain what a 'summary' contains, pagination, or how to get full messages.

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?

Description adds no meaning to parameters beyond the schema. Schema coverage is 50%, and the description does not compensate by explaining the options object or its subfields.

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 'List message summaries for a server' clearly states the action (list) and resource (message summaries) and scope (for a server). It distinguishes from sibling tools like get (full message) or search.

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?

No guidance on when to use this tool versus alternatives like search or get. No prerequisities or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MrNewDelhi/mailosaur-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server