MCP Emails

Cancel a previewed bulk operation

bulk_cancel

Idempotent

Cancel a previewed bulk email delete or move using its plan ID, ensuring the operation never runs. Records your decision instead of waiting for the 15-minute preview to expire.

Instructions

Decline a previewed bulk delete or move, so it can never run. Takes only the plan_id. Nothing in the mailbox changes. A preview would also expire on its own after 15 minutes; cancelling records the decision instead of leaving it implicit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`plan_id`	Yes	The plan_id returned with a bulk preview.

Output Schema

TableJSON Schema

Name	Required	Description
`card`	No	Which card this envelope renders. Always 'receipt' here.
`state`	No	Where the plan stands: executed, cancelled, expired or failed.
`receipt`	No	What the run actually did: headline, detail and the affected counts.
`dashboard_url`	No	Absolute link to the signed-in dashboard for this operation.
`schema_version`	No	Card envelope version. A client that does not know this version should fall back to dashboard_url.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "card": {
+      "description": "Which card this envelope renders. Always 'receipt' here.",
+      "type": "string"
+    },
+    "dashboard_url": {
+      "description": "Absolute link to the signed-in dashboard for this operation.",
+      "type": "string"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "description": "What the run actually did: headline, detail and the affected counts.",
+      "type": "object"
+    },
+    "schema_version": {
+      "description": "Card envelope version. A client that does not know this version should fall back to dashboard_url.",
+      "type": "integer"
+    },
+    "state": {
+      "description": "Where the plan stands: executed, cancelled, expired or failed.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.4Aug 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already give idempotentHint=true and destructiveHint=false, and the description reinforces this with 'Nothing in the mailbox changes'. It also adds new context about the 15-minute expiration and that cancellation 'records the decision', which goes beyond what the annotations state.

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 only a few sentences, with the essential action and consequence front-loaded. Every sentence provides a relevant detail: the decline action, the input scope, the non-mutating nature, and the expiry alternative. No filler or extraneous content.

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?

Given that the tool has a single parameter, an output schema, and annotations covering idempotency and safety, the description provides enough to call the tool correctly. It covers what action is taken, what won't change, and how the cancellation is recorded, leaving no critical gap for this simple use case.

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% and the only parameter, plan_id, is already fully described as a UUID returned from a bulk preview. The description only says 'Takes only the plan_id' which does not add new semantic meaning beyond the schema.

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 uses the specific verb 'Decline' and names the resource ('a previewed bulk delete or move'), then adds the consequence 'so it can never run' and distinguishes itself from bulk execution. It also clarifies the single input with 'Takes only the plan_id', which fully separates this from bulk_execute.

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 provides clear context: use it to decline a preview operation before it runs. It also explains an alternative, 'would also expire on its own after 15 minutes', implying the choice to cancel now or do nothing. However, it does not name a sibling like bulk_execute explicitly, so it lacks the exclusions of a full 5.

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