mcp-hey

by Sealjay

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

hey_delete_draft

DestructiveIdempotent

Permanently deletes a draft by ID without moving it to Trash. Use when you need to remove a draft irreversibly.

Instructions

Permanently delete a draft by ID. This does not move it to Trash — it is gone immediately, same as the trash icon in Hey's Drafts list. Returns {success, draftId, error?}. Irreversible; there is no hey_restore_draft. Use hey_list_emails(folder='drafts') first if you don't already have the draftId from hey_save_draft or hey_edit_draft.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "hey_delete_draft"
  }
}

Input Schema

Name	Required	Description	Default
`draft_id`	Yes	The draft's message ID, from hey_save_draft's draftId or hey_list_emails(folder='drafts')

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.0Sep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds what those hints cannot express: the delete bypasses Trash, is immediate and irreversible, and there is no restore counterpart. It also discloses the return shape ({success, draftId, error?}) despite no output schema existing.

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?

Four short sentences, front-loaded with the destructive semantic and irreversibility, then return shape, then prerequisite. No filler and nothing repeated.

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 one-parameter destructive tool with no output schema, the description covers effect (immediate, non-Trash), reversibility (none), return value, and how to obtain the ID. Nothing an agent needs to invoke it safely 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 description coverage is 100% and the schema already names the source of draftId, so the description's provenance note is largely redundant with structured data. It adds no format, validation, or ID-shape detail beyond what the schema provides; baseline 3 applies for a single fully documented parameter.

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 delete a draft by ID') and immediately scopes it against the sibling set by noting there is no hey_restore_draft. An agent can distinguish this from hey_save_draft / hey_edit_draft without opening any schema.

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?

Explicitly states the prerequisite path ('Use hey_list_emails(folder='drafts') first if you don't already have the draftId from hey_save_draft or hey_edit_draft'), and explicitly excludes the assumed undo path. Both when-to-use and when-not-to-rely-on-restore are covered.

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