Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete thread

delete_thread
DestructiveIdempotent

Permanently deletes an entire email thread and its messages; this action cannot be undone.

Instructions

Permanently delete a whole thread and its messages. This cannot be undone.

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>",
      "thread_id": "<thread_id>"
    },
    "name": "delete_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.
thread_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so 'permanently' and 'cannot be undone' mostly restate what the agent already knows. The genuinely additive detail is the cascade disclosure that the thread's messages are also destroyed, which goes beyond the annotations. Missing: what happens when the thread does not exist, and whether any auth or scope constraints beyond inbox_id apply.

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?

Two short sentences, front-loaded with the action and immediately followed by irreversibility. No filler, though the second sentence is largely redundant with the destructive annotation.

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?

For a destructive, irreversible operation with no output schema and half-documented parameters, the description is thin. The cascade behavior is covered, but error semantics (nonexistent thread, cross-inbox rejection) and the inbox/thread relationship are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: inbox_id is documented in the schema, but thread_id is undocumented in both schema and description, and the description adds no parameter meaning at all. It never clarifies whether the thread must belong to the given inbox or how ids are formatted.

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?

A specific verb plus resource: 'Permanently delete a whole thread and its messages' tells an agent exactly what is removed and at what scope. Scoping to a whole thread implicitly distinguishes it from single-message deletion, though it never names a sibling as an alternative.

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?

The phrase 'a whole thread and its messages' implies when this tool is appropriate (thread-level bulk deletion rather than per-message), but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is only implied by scope wording.

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