Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

Delete inbox

delete_inbox
DestructiveIdempotent

Delete a disposable inbox and all its emails once signup, login, or email-flow testing is complete, removing temporary address data.

Instructions

Delete an inbox and its emails when the task is done.

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": {
      "inbox_id": "<inbox_id>"
    },
    "name": "delete_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe inbox to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description adds non-obvious context beyond the annotations: that emails contained in the inbox are also destroyed. It stops short of stating irreversibility or recovery options, which keeps it from a 5.

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?

One sentence, front-loaded with the verb and resource, with zero filler wording. Nothing is repeated from the title or schema.

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 single-parameter destructive tool with rich annotations and no output schema, the description covers purpose and the cascade side effect adequately. It omits permanence, permission requirements, and error behavior, which are minor gaps given annotation coverage.

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 single inbox_id parameter has 100% schema coverage with its own description, so the schema carries the parameter burden. The description says only 'an inbox' and adds no identifier format, source, or lookup guidance beyond the schema - the baseline 3.

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?

'Delete an inbox and its emails' is a specific verb plus resource with an important scope detail: the deletion cascades to emails. It is clearly distinct from siblings like create_inbox or list_inboxes, though the description never explicitly contrasts them.

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?

'When the task is done' gives a timing hint that implies this is cleanup at the end of a workflow, which is useful context. However, it names no alternatives and gives no exclusions or preconditions (e.g., whether unread emails must be handled first).

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