best-tempmail-mcp

Delete an inbox

delete_inbox

Remove a disposable inbox and its contents immediately, bypassing the automatic expiration wait.

Instructions

Delete an inbox and everything in it. Inboxes expire on their own, so this is only needed when the user wants it gone immediately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "delete_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	The inbox address to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses the destructive and irreversible nature of the operation ('Delete an inbox and everything in it'), which is important since no annotations are provided. It also mentions the immediate effect, though it doesn't explicitly state irreversibility, but the implication is strong.

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 concise, using just two sentences to convey the action, scope, and usage context. No redundant or extraneous information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides sufficient context for a simple delete operation: it explains the action, the scope (everything in the inbox), and the typical usage scenario. No output schema is needed, and the parameter is clearly defined, so the description is complete.

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 only parameter 'address' is fully described in the schema ('The inbox address to delete'), and the description does not add further semantic detail beyond that. Schema coverage is 100%, so the baseline of 3 is appropriate.

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 clearly states the action ('Delete an inbox and everything in it') with a specific verb and object. It distinguishes itself from sibling tools like create_inbox without needing to name them.

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

Usage Guidelines5/5

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

It explicitly explains when to use the tool: 'only needed when the user wants it gone immediately', noting that inboxes normally expire on their own, which provides clear guidance on when this tool is appropriate versus relying on expiration.

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

Deploy Server