Skip to main content
Glama

get_inbox

Retrieve inbox details and list received emails to monitor incoming messages and extract verification codes for automated sign-up workflows.

Instructions

Get inbox details and list of received emails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_idYesThe inbox ID

Implementation Reference

  • Implementation of the 'get_inbox' tool, which fetches details of a specific inbox using an inbox_id.
    server.tool(
      "get_inbox",
      "Get inbox details and list of received emails.",
      {
        inbox_id: z.string().describe("The inbox ID"),
      },
      async ({ inbox_id }) => {
        const result = await blipFetch(`/v1/inboxes/${inbox_id}`);
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
Behavior2/5

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

With no annotations provided, description carries full behavioral burden but offers minimal disclosure. States it returns a list, but omits pagination behavior, email count limits, whether emails are marked as read, error handling for invalid IDs, or content truncation policies.

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?

Single efficient sentence with no redundancy. Front-loaded with verb and object. However, brevity is excessive given lack of annotations and output schema, leaving gaps that could have been filled with one more sentence.

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?

Adequate for a single-parameter retrieval tool, mentioning both inbox metadata and email list return values. However, with no output schema and no annotations, it should specify return structure, pagination, or email content depth (headers vs body).

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 fully described in schema as 'The inbox ID'). Description adds no parameter-specific guidance, so baseline 3 applies per rules for high-coverage schemas.

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?

Clear verb 'Get' with specific resources 'inbox details' and 'received emails'. Implicitly distinguishes from sibling list_inboxes (which lists all inboxes without ID) and read_email (which reads a single email rather than returning a list).

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 versus alternatives like wait_for_email or read_email. Does not mention prerequisites (e.g., inbox must exist) or expected workflow.

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