Skip to main content
Glama
Sealjay

mcp-hey

hey_pop_bubble

Remove an email from the bubble view, returning it to the inbox without deleting or archiving it.

Instructions

Pop (dismiss) a bubbled-up email so it sinks back into the Imbox. The email is not deleted or archived — it just stops being pinned at the top.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
posting_idYesThe posting ID to pop/unbubble

Implementation Reference

  • src/index.ts:938-952 (registration)
    Tool registration for 'hey_pop_bubble' in the tools array with name 'hey_pop_bubble', description and inputSchema requiring posting_id.
    {
      name: "hey_pop_bubble",
      description:
        "Pop (dismiss) a bubbled-up email so it sinks back into the Imbox. The email is not deleted or archived — it just stops being pinned at the top.",
      inputSchema: {
        type: "object" as const,
        properties: {
          posting_id: {
            type: "string",
            description: "The posting ID to pop/unbubble",
          },
        },
        required: ["posting_id"],
      },
    },
  • Switch-case handler in CallToolRequestSchema that validates posting_id and calls popBubble(postingId).
    case "hey_pop_bubble": {
      const postingId = validateId(args?.posting_id)
      if (!postingId) {
        return {
          content: [
            {
              type: "text",
              text: "Error: posting_id is required and must be valid",
            },
          ],
          isError: true,
        }
      }
      result = await popBubble(postingId)
      break
    }
  • Core handler function popBubble that performs a DELETE request to /postings/bubble_up endpoint with the posting ID and invalidates cache on success.
    /**
     * Pop (dismiss) a bubbled-up email so it sinks back into the Imbox.
     */
    export async function popBubble(postingId: string): Promise<OrganiseResult> {
      if (!postingId) {
        return { success: false, error: "Posting ID is required" }
      }
    
      try {
        const endpoint = `/postings/bubble_up?posting_ids[]=${postingId}`
        const response = await withCsrfRetry(() => heyClient.delete(endpoint))
    
        return organiseResponseToResult(response, () =>
          invalidateForAction("bubble_up", postingId),
        )
      } catch (err) {
        return { success: false, error: toUserError(err) }
      }
    }
  • Input schema for hey_pop_bubble tool requiring posting_id (string).
    inputSchema: {
      type: "object" as const,
      properties: {
        posting_id: {
          type: "string",
          description: "The posting ID to pop/unbubble",
        },
      },
      required: ["posting_id"],
    },
  • Cache invalidation via invalidateForAction('bubble_up', postingId) after successful pop.
    export async function popBubble(postingId: string): Promise<OrganiseResult> {
      if (!postingId) {
        return { success: false, error: "Posting ID is required" }
      }
    
      try {
        const endpoint = `/postings/bubble_up?posting_ids[]=${postingId}`
        const response = await withCsrfRetry(() => heyClient.delete(endpoint))
    
        return organiseResponseToResult(response, () =>
          invalidateForAction("bubble_up", postingId),
        )
      } catch (err) {
        return { success: false, error: toUserError(err) }
      }
    }
    
    /**
     * Schedule an email to bubble up ONLY if there's no reply by a specific date.
     */
    export async function bubbleUpIfNoReply(
      postingId: string,
Behavior4/5

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

With no annotations, the description adequately discloses that the email is not deleted or archived, only unpinned. However, it does not mention potential side effects like read status changes.

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 concise, front-loaded sentences with no unnecessary words. 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?

For a simple tool with one parameter, the description covers what the tool does and what it does not do, making it complete for an agent to invoke correctly.

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 parameter is described adequately. The description adds minimal extra meaning beyond the schema's 'posting ID to pop/unbubble'.

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 specific action ('Pop (dismiss) a bubbled-up email') and its effect ('sinks back into the Imbox'), distinguishing it from siblings like hey_bubble_up.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when you want to unbubble an email, but does not explicitly compare to alternatives like hey_trash or hey_archive, nor provide when-not-to-use scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sealjay/mcp-hey'

If you have feedback or need assistance with the MCP directory API, please join our Discord server