mcp-hey

by Sealjay

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

hey_pop_bubble

Idempotent

Pop a bubbled email thread to send it back to the Imbox without deletion. Requires the thread's topic ID.

Instructions

Pop (dismiss) a bubbled-up email thread so it sinks back into the Imbox. The thread is not deleted — it just stops being pinned at the top. Returns {success, error?}. Requires the thread's topic_id (use topic_id from any list operation); posting IDs are not accepted.

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": {
      "topic_id": "<topic_id>"
    },
    "name": "hey_pop_bubble"
  }
}

Input Schema

Name	Required	Description	Default
`topic_id`	Yes	The topic ID (thread ID) to pop/unbubble. Use the `topicId` field from hey_list_* responses (NOT `postingId` — that's a different ID and will 404).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.4.1May 12, 2026

removedInput schema / properties / posting_id

Removed value: -{
-  "description": "The topic or posting ID to pop/unbubble (use topicId preferred)",
-  "type": "string"
-}

addedInput schema / properties / topic_id

Added value: +{
+  "description": "The topic ID (thread ID) to pop/unbubble. Use the `topicId` field from hey_list_* responses (NOT `postingId` — that's a different ID and will 404).",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "posting_id"
-]New value: +[
+  "topic_id"
+]

Changed1 schema field changedv0.3.0May 9, 2026

changedInput schema / properties / posting_id / description

Previous value: -"The posting ID to pop/unbubble"New value: +"The topic or posting ID to pop/unbubble (use topicId preferred)"

First observedv0.1.0May 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses idempotent behavior (consistent with annotations), non-destructive nature, return value {success, error?}, and error condition for incorrect ID types. Adds value beyond annotations.

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?

Concise two-sentence description front-loaded with action and effect, no wasted words.

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 simple 1-parameter tool without output schema, the description covers purpose, usage, prerequisites, return type, and error cases completely.

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?

Input schema already covers 100% of parameters with detailed guidance on topic_id vs postingId. Description reinforces but adds minimal new information beyond 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 clearly states the tool pops/dismisses a bubbled email thread, distinguishing it from sibling tools like hey_bubble_up by specifying the reverse action.

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?

Provides explicit instructions on when to use, including the prerequisite of using topic_id (not posting_id) and clarifies that the thread is not deleted, just unpinned.

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