Skip to main content
Glama
lobster-kit

mcp-server-lobstermail

by lobster-kit

Delete Inbox

delete_inbox

Soft-delete an inbox with a 7-day grace period before permanent removal. Manage email inboxes by initiating deletion while allowing recovery during the grace window.

Instructions

Soft-delete an inbox. It enters a 7-day grace period before permanent deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_idYesInbox ID to delete

Implementation Reference

  • The delete_inbox tool registration and handler logic. It uses the LobsterMail client to perform the deletion.
    server.registerTool('delete_inbox', {
      title: 'Delete Inbox',
      description: 'Soft-delete an inbox. It enters a 7-day grace period before permanent deletion.',
      inputSchema: {
        inbox_id: z.string().describe('Inbox ID to delete'),
      },
    }, async ({ inbox_id }) => {
      const lm = await getClient();
      await lm.deleteInbox(inbox_id);
    
      return {
        content: [
          {
            type: 'text' as const,
            text: `Inbox ${inbox_id} has been soft-deleted. It will be permanently removed after 7 days.`,
          },
        ],
      };
Behavior4/5

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

No annotations provided, so description carries full burden. It successfully discloses: (1) the operation is a soft-delete (not immediate hard delete), (2) the 7-day grace period safety window, and (3) eventual permanent deletion. Could improve by stating what happens to emails inside the inbox or how to restore during the grace period.

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?

Two sentences, zero waste. First sentence front-loads the action (Soft-delete), second sentence provides critical behavioral context (grace period). No redundancy with schema or name.

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?

Adequate for a single-parameter deletion tool. Explains the mutation behavior and safety mechanism. No output schema exists, so return values need not be explained. Minor gap: does not clarify if emails are cascaded-soft-deleted or remain accessible.

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% (inbox_id is well-described in schema), establishing baseline 3. Description does not mention inbox_id explicitly or add syntax guidance beyond the schema, but none is needed given the complete schema documentation.

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?

Excellent clarity: 'Soft-delete' specifies the exact operation type (distinguishing from permanent deletion), 'an inbox' identifies the resource, and the grace period details scope the behavior. Clearly distinguishes from sibling create_inbox and read operations like list_inboxes.

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 grace period description implies recoverability (suggesting when to use: temporary removal), but lacks explicit guidance such as 'Use when you need to recover the inbox later' or warnings like 'Do not use if immediate permanent deletion is required.'

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/lobster-kit/mcp-server-lobstermail'

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