Skip to main content
Glama
Sign In

Busymail

by app.busymail
OverviewDiscussionsAdmin

Unarchive a conversation

unarchive_conversation

Bring one archived conversation back to the feed, and queue a move of its messages back to the user's INBOX. The reply's result field says unarchived, or already_in_feed when the conversation was not archived - a reply to an archived thread brings it back automatically without moving its mail, so the move is queued either way and is what reconciles them. messages_queued_to_move counts the messages queued.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "unarchive_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesThe conversation's UUID, from list_feed, get_cluster or search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Since no annotations exist, the description carries the full burden of behavioral transparency. It details complex process outcomes like the queuing mechanism and the specific return values ('unarchived' or 'already_in_feed'), which is highly valuable.

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

Conciseness3/5

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

The definition is slightly dense and long-winded, focusing heavily on technical reconciliation details. While all information is relevant, it could be structured more succinctly for rapid agent consumption.

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 the lack of an output schema, the description provides critical information about the result field state. It covers the entire logical flow of the operation, from the message move to the final result status.

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 coverage is 100%, so baseline is 3. However, the description clarifies that the move is 'queued either way' and explains the meaning of 'messages_queued_to_move,' which adds semantic value beyond the simple parameter definition.

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 defines the action (bringing a conversation back to the feed and moving its messages) and differentiates itself from potential cluster-level unarchiving siblings.

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?

It provides specific behavior regarding automatic actions, stating that replying to an archived thread triggers a move without explicit parameter handling. This gives a clear operational context for its use.

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

All Busymail toolsInspect
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