best-tempmail-mcp

Create a disposable email inbox

create_inbox

Create a temporary email address to receive mail during signups or trials. Returns the address and its expiration time.

Instructions

Create a temporary email address that can receive mail. Use this when the user needs an email address for a signup, a trial, or anything they do not want to give a real address to. Returns the address and when it expires.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	No	Optional domain from list_domains. Random if omitted.
`username`	No	Optional local part, for example 'my-test'. Lowercase letters, digits, dot, underscore and hyphen only. Random if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden, and it does well: it states that the inbox is temporary, can receive mail, and that the response includes the address and expiration time. It does not cover every operational detail such as cleanup or duplicate-name behavior, but the essential lifecycle is disclosed.

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?

The description is three tight sentences: the core action, the usage context, and the return value. Every sentence adds information, and there is no redundant or filler content.

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?

For a simple create tool with no required parameters and no output schema, the description covers what the tool does, when to use it, and what the response contains. It could mention interactions with sibling tools or what happens if a requested domain/username is unavailable, but those are minor gaps given the schema already documents allowed values.

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?

The schema already provides 100% coverage of both optional parameters, including the allowed characters for username and the fact that domain comes from list_domains. The description adds no parameter-specific meaning, so it stays at the baseline expected when the schema is fully documented.

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 names a specific action and resource: creating a temporary email address that can receive mail. It also clarifies the intended use case (signups, trials, avoiding real addresses), which makes the tool's role unambiguous compared to siblings like list_messages, delete_inbox, and wait_for_email.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool: when the user needs an email address for a signup, trial, or similar situation. It does not mention alternatives or exclusions, but because this is the only creation-focused sibling, the guidance is still clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server