mcp-hey

Overview Schema Source Related Servers Discussions Admin

hey_set_status

DestructiveIdempotent

Change an email thread's status: trash (remove from inbox), spam (block sender), restore (recover from trash), unspam (restore from spam).

Instructions

Change an email thread's status. Returns {success, error?}. Trash and spam are reversible via restore and unspam actions respectively. DESTRUCTIVE: trash removes from Imbox, spam blocks the sender. Paper Trail bundles (postingId-only items with no thread) support action=trash only; spam/restore/unspam on a bundle return an explicit error pointing to the bundle's individual entries.

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "hey_set_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The topic/thread ID (use topicId from list operations). For Paper Trail bundles, pass the postingId — trash works via a posting-based fallback, other actions return an error.
`action`	Yes	The status action: trash (move to Trash), restore (recover from Trash), spam (mark as spam and block sender), unspam (restore from spam folder)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.1May 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide destructiveHint and idempotentHint; description adds concrete details: 'trash removes from Imbox', 'spam blocks the sender', and error handling for bundles. No contradiction.

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?

Two dense sentences with no unnecessary words. Front-loaded with purpose, then return format, then edge cases. Highly efficient.

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?

Addresses return format, destructive effects, reversibility, and special case (bundles). No output schema needed given simplicity. Complete for minimum viable understanding.

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

Parameters4/5

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

Schema covers both parameters with descriptions (100% coverage). Description adds context on id parameter usage (topicId vs postingId) and action effects, but enum already lists actions.

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?

Description clearly states it changes an email thread's status, which is a specific verb+resource. It distinguishes from sibling tools like hey_label or hey_collection by focusing on status actions (trash, spam, etc.).

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?

Provides explicit context on reversibility (trash/spam), destructive effects, and bundle-specific limitations (only trash works on bundles). Could mention when to use this vs other status-changing tools like hey_screen, but the domain is different.

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