Skip to main content
Glama

create_inbox

Create a disposable email inbox for AI agents to receive verification emails and extract OTP codes during automated sign-up processes.

Instructions

Create a new disposable email inbox. Returns the inbox ID and email address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoCustom address slug (e.g. 'mytest' for mytest@useblip.email)
domainNoEmail domain (defaults to useblip.email)
ttl_minutesNoHow long the inbox should live, in minutes (AGENT tier only, max 90 days). Defaults to 60 minutes if omitted.

Implementation Reference

  • Handler function that executes the logic to create an inbox by sending a POST request to the Blip API.
    async ({ slug, domain, ttl_minutes }) => {
      const body: Record<string, unknown> = {};
      if (slug) body.slug = slug;
      if (domain) body.domain = domain;
      if (ttl_minutes !== undefined) body.windowMinutes = ttl_minutes;
    
      const result = await blipFetch("/v1/inboxes", {
        method: "POST",
        body: JSON.stringify(body),
      });
    
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool registration for 'create_inbox' with Zod input schema.
    server.tool(
      "create_inbox",
      "Create a new disposable email inbox. Returns the inbox ID and email address.",
      {
        slug: z
          .string()
          .optional()
          .describe("Custom address slug (e.g. 'mytest' for mytest@useblip.email)"),
        domain: z
          .string()
          .optional()
          .describe("Email domain (defaults to useblip.email)"),
        ttl_minutes: z
          .number()
          .optional()
          .describe(
            "How long the inbox should live, in minutes (AGENT tier only, max 90 days). Defaults to 60 minutes if omitted."
          ),
      },
      async ({ slug, domain, ttl_minutes }) => {
        const body: Record<string, unknown> = {};
        if (slug) body.slug = slug;
        if (domain) body.domain = domain;
        if (ttl_minutes !== undefined) body.windowMinutes = ttl_minutes;
    
        const result = await blipFetch("/v1/inboxes", {
          method: "POST",
          body: JSON.stringify(body),
        });
    
        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 provided, so description carries full burden. It discloses the return values and characterizes the inbox as 'disposable' (hinting at temporary nature), but omits side effects, idempotency rules for duplicate slugs, and AGENT tier restrictions noted in the parameter schema.

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 precise sentences with zero redundancy: first states the action, second states the return value. Front-loaded and appropriately sized for a simple creation tool.

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?

Given 100% schema coverage and the tool's straightforward purpose, the description is complete. It compensates for the lack of formal output schema by documenting return values, though it could mention the temporary/disposable nature implications more explicitly.

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?

Input schema has 100% description coverage, establishing baseline 3. The description adds no explicit parameter semantics but mentions return values (inbox ID and email address), which compensates somewhat for the missing output schema.

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 'Create' with clear resource 'disposable email inbox'. The modifier 'new' and 'disposable' effectively distinguish this from sibling tools like get_inbox or 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?

Provides implicit usage through 'Returns the inbox ID' indicating when to invoke it, but lacks explicit guidance on when to prefer this over get_inbox or prerequisites like tier requirements mentioned in the ttl_minutes schema.

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