Skip to main content
Glama

list_inboxes

List all email inboxes to enable AI agents to send, receive, and search messages across threads.

Instructions

List all email inboxes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • mcp/index.js:151-159 (registration)
    The tool 'list_inboxes' is registered via server.tool() with empty schema and an async handler that calls GET /v1/inboxes via the api helper.
    server.tool(
      'list_inboxes',
      'List all email inboxes',
      {},
      async () => {
        const result = await api('GET', '/v1/inboxes');
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      }
    );
  • Handler function for list_inboxes: calls api('GET', '/v1/inboxes') and returns the JSON result as text content.
    async () => {
      const result = await api('GET', '/v1/inboxes');
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Input schema for list_inboxes - an empty object {} since this tool takes no parameters.
    {},
  • Node.js SDK helper method listInboxes() that calls the same API endpoint GET /v1/inboxes.
    listInboxes() {
      return this._request('GET', '/v1/inboxes');
    }
  • Python SDK helper method list_inboxes() that calls the same API endpoint GET /v1/inboxes.
    def list_inboxes(self):
        return self._request("GET", "/v1/inboxes")
Behavior2/5

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

No annotations are provided, and the description is minimal. It does not disclose behavioral traits like authentication needs, rate limits, or whether the operation is read-only. 'List all email inboxes' implies a read operation, but no further details are given.

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 extraneous words. Perfectly concise and front-loaded with the action.

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?

For a simple tool with no parameters, the description is minimally complete. However, it lacks information about the output format or any edge cases (e.g., empty inbox list). Without an output schema, the description should provide more context on what 'list' returns.

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?

The input schema has zero parameters, so schema coverage is 100%. The description adds the word 'all', implying no filtering, which provides marginal semantic value beyond the schema. Per rules, baseline for 0 params is 4.

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?

The description clearly states the verb 'list' and the resource 'email inboxes', differentiating from sibling tools like 'list_messages' or 'create_inbox'. However, it lacks additional context that might clarify scope or behavior.

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 such as 'search_emails' or 'list_messages'. The description does not mention prerequisites, limitations, or context of use.

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/joansongjr/clawaimail'

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