Inbox Triage

Snooze messages

snooze_messages

Idempotent

Hides the person's messages from show_inbox until a time you give. Messages the person picked: pass each row's inboxId and messageId from show_inbox (the id block at the end of its text, or structuredContent.rows), usually by row number ("archive 2 and 5"). Or pass sender { inboxId, email } to act on that sender's mail still in the inbox, like "archive everything from 2" after review_unsubscribes (up to 50 newest per call). Needs until, an ISO time with a UTC offset. Snooze is local to Inbox Triage: nothing changes in the mail app, and snoozed mail still shows under show_inbox filter "all", list_messages and get_message. Use it only when the person asks to snooze or be reminded. Mail from a VIP is skipped when you act on several messages. Act on a VIP's message alone, and only after the person agrees: in apps that can prompt the person, they are asked directly; otherwise ask in chat and pass vipConfirmed:true. Reporting spam is not done here: it goes through propose_mark_spam then confirm_mark_spam, one message at a time. Work on your own only on a clear instruction or a saved agentRules rule; otherwise suggest and wait. The result has an undoId for undo_view_action, which works once, for 7 days; report counts and the undoId.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snooze_messages"
  }
}

Input Schema

Name	Required	Description
`items`	No
`until`	No	ISO time with a UTC offset to bring the messages back, e.g. 2026-09-28T09:00:00-05:00. Within a year.
`sender`	No	Instead of items: every message from this sender still in the inbox
`vipConfirmed`	No	true only after the person agreed in chat to act on this one VIP message

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by stating snooze is local to Inbox Triage and nothing changes in the mail app, that snoozed mail still appears under show_inbox filter "all", list_messages and get_message, that VIP mail is skipped in bulk actions, and that the returned undoId works once for 7 days. That is exactly the side-effect, reversibility and visibility context the annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core effect and id sourcing, then escalations and reporting. It is dense and long for a four-parameter tool, and the VIP/confirmation paragraph could be tightened, but nearly every sentence carries operational information.

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?

Covers sourcing the ids, the items-vs-sender alternatives, the required time format, VIP confirmation behavior, the undo window, and what to report back. With no output schema, it still tells the agent what the result contains (counts, undoId), leaving nothing essential unstated.

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?

Adds real meaning over the schema: it explains where inboxId/messageId come from (the id block at the end of show_inbox text, or structuredContent.rows), gives the row-number phrasing people use, and notes the sender form caps at 50 newest per call, a limit the schema does not state. It repeats the schema's ISO-with-offset detail for until rather than adding to it, so not quite a 5.

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?

Opens with a specific verb and effect: it hides a person's messages from show_inbox until a given time, which is clearly distinct from archive_messages, trash_messages, and unsnooze_messages. It also draws the boundary against spam reporting by naming propose_mark_spam/confirm_mark_spam as the correct path.

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 gates use to requests to snooze or be reminded, says to work autonomously only on a clear instruction or a saved agentRules rule, and otherwise suggest and wait. It names alternatives (spam goes to propose_mark_spam then confirm_mark_spam, one message at a time) and the VIP escalation path.

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

All Inbox Triage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?