Skip to main content
Glama
Sign In
mcp-hey

mcp-hey

by Sealjay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hey_bubble_up

Idempotent

Schedule an email thread to reappear at a chosen time using the thread's topic ID and a time slot such as 'today' or 'next week'.

Instructions

Schedule an email thread to bubble up (reappear) at a specific time. Returns {success, error?}. Reversible via hey_pop_bubble. Requires the thread's topic_id (use topic_id from any list operation); posting IDs are not accepted and will 404.

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>",
      "slot": "<slot>"
    },
    "name": "hey_bubble_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Required when slot is 'custom', ignored otherwise.
slotYesWhen to bubble up: now (immediately), today (evening), tomorrow (morning), weekend (Saturday), next_week (Monday), surprise_me (random), custom (specific date - requires 'date' parameter)
topic_idYesThe topic ID (thread ID) to schedule. 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.

  1. Changed3 schema fields changedv0.4.1
    • removedInput schema / properties / posting_id
      Removed value: -{
-  "description": "The topic or posting ID to schedule (use topicId for 'now' slot)",
-  "type": "string"
-}
    • addedInput schema / properties / topic_id
      Added value: +{
+  "description": "The topic ID (thread ID) to schedule. 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",
-  "slot"
-]New value: +[
+  "topic_id",
+  "slot"
+]
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / posting_id / description
      Previous value: -"The posting ID to schedule"New value: +"The topic or posting ID to schedule (use topicId for 'now' slot)"
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Beyond annotations (idempotent, non-destructive), description adds return format {success, error?} and the critical constraint that posting IDs are not accepted. No contradiction with 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?

Two sentences with all critical information front-loaded. No redundant text, every sentence adds value.

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 annotations, schema completeness, and no output schema, the description covers all necessary aspects: purpose, parameters, constraints, return format, and reversibility.

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

Parameters5/5

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

Schema coverage is 100%, and description adds crucial context: topic_id must come from list operations, slot options are explained, and date parameter requirement for custom slot. The distinction between topic_id and postingId is essential and well clarified.

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?

Explicitly states the action (schedule an email thread to bubble up) and resource (email thread). Differentiates from sibling hey_pop_bubble by mentioning reversibility.

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?

Clearly states when to use (schedule a thread to reappear) and what not to use (posting IDs cause 404). Mentions reversible alternative hey_pop_bubble but does not contrast with hey_bubble_up_if_no_reply.

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

Deploy Server

Other Tools