Cooper Email

Delete a thread

cooper_delete_thread

DestructiveIdempotent

Use this when a whole conversation should be removed permanently. Requires auth. Deletes every message in the thread, plus attachment bytes, search rows, the assignment, and the folder row. Owner tasks and updates are left in place. This cannot be undone. To keep the thread for 30 days, move it to trash with cooper_update_thread or cooper_move_threads instead. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required). Returns {id, deleted:true, messages_deleted}. An unknown thread returns HTTP 404 thread_not_found. Another account's inbox returns inbox_not_found.

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": "cooper_delete_thread"
  }
}

Input Schema

Name	Required	Description	Default
`inbox_id`	Yes	Inbox id (inb_…), username, or full email address owned by this key
`thread_id`	Yes	Thread id (thr_…) to delete

Output Schema

Name	Required	Description
`id`	No	Stable id of the returned object. Pass it to the matching get, update, or delete tool.
`deleted`	No	True when the object was deleted.
`messages_deleted`	No	How many messages were deleted with it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Deletion result for the thread.",
+  "properties": {
+    "deleted": {
+      "description": "True when the object was deleted."
+    },
+    "id": {
+      "description": "Stable id of the returned object. Pass it to the matching get, update, or delete tool."
+    },
+    "messages_deleted": {
+      "description": "How many messages were deleted with it."
+    }
+  },
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds real value beyond them: auth requirement, the exact set of related records destroyed, what is deliberately left intact (owner tasks and updates), irreversibility, and the specific error outcomes (thread_not_found, inbox_not_found) with their HTTP mapping.

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?

Front-loads the decision criterion, then consequences, then the explicit 'Inputs:' and 'Returns:' blocks. Every sentence carries information — destruction scope, irreversibility, alternative, errors — with no filler.

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?

For a two-parameter destructive tool, the definition covers safety, side effects, alternatives, error cases, and the return shape ({id, deleted:true, messages_deleted}). An output schema exists and annotations cover read-only/destructive semantics, so nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description's inline restatement of inbox_id (id, username, or email) largely duplicates the schema text. Its only added semantic is tying parameter misuse to concrete failures — an unknown thread yields 404 thread_not_found and another account's inbox yields inbox_not_found.

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?

States a specific verb and resource (permanently remove an entire conversation) and immediately enumerates what that entails: all messages, attachment bytes, search rows, the assignment, and the folder row. It distinguishes itself from sibling mutations by naming cooper_update_thread and cooper_move_threads as the non-destructive alternatives.

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?

Gives an explicit trigger ('when a whole conversation should be removed permanently') and an explicit exclusion with the alternative tools ('To keep the thread for 30 days, move it to trash with cooper_update_thread or cooper_move_threads instead'). The decision between permanent deletion and trashing is fully routed.

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

All Cooper Email tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.