Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

mailosaur_messages_delete_all

Delete all messages and attachments from a Mailosaur server to clean up test data.

Instructions

Permanently delete all messages and attachments on a server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesMailosaur server ID.
confirmNo

Implementation Reference

  • src/index.ts:238-250 (registration)
    Registration of the 'mailosaur_messages_delete_all' tool via server.tool(), with description, input schema (server string + optional confirm boolean), and handler.
    server.tool(
  "mailosaur_messages_delete_all",
  "Permanently delete all messages and attachments on a server.",
  {
    server: z.string().describe("Mailosaur server ID."),
    confirm: z.boolean().optional()
  },
  async ({ server, confirm }) => {
    requireConfirm(confirm, `delete all messages on server ${server}`);
    await mailosaur.messages.deleteAll(server);
    return emptyResponse("All server messages deleted.");
  }
);
  • src/index.ts:245-249 (handler)
    Handler for mailosaur_messages_delete_all: requires confirmation, then calls mailosaur.messages.deleteAll(server) and returns success response.
    async ({ server, confirm }) => {
  requireConfirm(confirm, `delete all messages on server ${server}`);
  await mailosaur.messages.deleteAll(server);
  return emptyResponse("All server messages deleted.");
}
  • src/index.ts:241-243 (schema)
    Input schema for the tool: 'server' (string) and optional 'confirm' (boolean).
    {
  server: z.string().describe("Mailosaur server ID."),
  confirm: z.boolean().optional()

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

The description states 'Permanently delete' indicating a destructive action, but with no annotations provided, it does not disclose additional behavioral traits such as whether permission checks exist, rate limits, or if the deletion triggers cascading effects. It carries the full burden but provides minimal insight.

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?

The description is a single concise sentence, front-loading the key action and resource. While it could include more context without much length, it is appropriately sized and clear.

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 the complexity (simple delete-all operation), no output schema, and no annotations, the description lacks crucial context: it does not explain the role of the 'confirm' parameter, whether the deletion is reversible, or what the response looks like. It is incomplete for a successful invocation.

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?

The input schema has 50% coverage (only 'server' has a description), and the tool description adds no meaning beyond the schema. It does not explain the purpose or role of the parameters, especially failing to mention the 'confirm' boolean parameter which is critical for the operation.

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 uses a specific verb 'delete' and identifies the resource 'all messages and attachments' with a scope 'on a server', clearly distinguishing it from sibling tools like 'mailosaur_messages_delete' which likely deletes a single message.

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 is provided on when to use this tool versus alternatives like 'mailosaur_messages_delete'. There is no mention of prerequisites, limitations, or when not to use it.

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