Skip to main content
Glama
lobster-kit

mcp-server-lobstermail

by lobster-kit

List Inboxes

list_inboxes

Retrieve all active email inboxes for your LobsterMail account to manage email tools within AI agents.

Instructions

List all active inboxes for this account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration and implementation handler for 'list_inboxes'. It retrieves the LobsterMail client and calls the listInboxes method.
    server.registerTool('list_inboxes', {
      title: 'List Inboxes',
      description: 'List all active inboxes for this account.',
      inputSchema: {},
    }, async () => {
      const lm = await getClient();
      const inboxes = await lm.listInboxes();
    
      if (inboxes.length === 0) {
        return {
          content: [{ type: 'text' as const, text: 'No inboxes found. Use create_inbox to create one.' }],
        };
      }
    
      for (const inbox of inboxes) {
        cacheInbox(inbox);
      }
Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose return format, pagination behavior, rate limits, or what 'active' means (vs deleted/archived). It only states the basic action.

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?

Single sentence with no waste. Front-loaded with the action verb. Every word earns its place.

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

Completeness3/5

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

While the action is clear for a zero-parameter tool, the lack of output schema means the description should ideally explain the return structure (e.g., array of inbox objects). Instead, it provides only the minimal action statement.

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

Parameters4/5

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

Input schema has zero parameters, which per guidelines establishes a baseline of 4. The description appropriately reflects this by not inventing non-existent parameters.

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

Purpose4/5

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

States specific verb (List), resource (inboxes), and scope (all active, for this account). The word 'all' effectively distinguishes from sibling 'check_inbox' (which implies singular checking), though it doesn't explicitly name the alternative.

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?

Provides implied usage through the 'all' scope, signaling to retrieve the complete inventory rather than checking a specific one. However, it lacks explicit 'when to use vs alternatives' guidance or prerequisites.

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