Skip to main content
Glama

list_inboxes

Retrieve all active disposable email inboxes associated with your API key to manage email verification and communication tasks.

Instructions

List all active inboxes for the current API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_inboxes' tool, which fetches data from the '/v1/inboxes' endpoint using the `blipFetch` helper function.
    server.tool(
      "list_inboxes",
      "List all active inboxes for the current API key.",
      {},
      async () => {
        const result = await blipFetch("/v1/inboxes");
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It mentions 'active' status and 'current API key' scope, but doesn't clarify what constitutes 'active' vs inactive/deleted states, pagination behavior, or response structure. No contradictions with annotations (none exist).

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 zero waste. Front-loaded with action verb 'List'. Every phrase earns its place: 'all active' defines scope, 'inboxes' identifies resource, 'for the current API key' clarifies authorization context. No redundant or filler text.

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?

Complete enough for a zero-parameter list operation. The description covers the core operation scope and auth context. Lacks output format details (no output schema exists), but 'List' implies collection return. Sufficient for low-complexity read operation.

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 contains zero parameters (empty properties object). Per calibration rules, zero parameters establishes a baseline of 4. The description appropriately requires no additional parameter clarification since no inputs are expected.

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 specific verb 'List' with clear resource 'inboxes' and scope qualifier 'all active'. The phrase 'for the current API key' distinguishes it from siblings like get_inbox (which likely retrieves a specific inbox) and scopes the operation appropriately to the authentication context.

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 description implies usage by specifying 'all active' (suggesting bulk retrieval), but lacks explicit guidance on when to prefer this over get_inbox for specific inbox retrieval, or whether this includes pagination/rate limiting considerations. No explicit 'when-not' or alternative recommendations provided.

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/blipemail/blip'

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