Skip to main content
Glama
Sign In

Busymail

by app.busymail
OverviewDiscussionsAdmin

Unarchive a cluster

unarchive_cluster

Bring a cluster's archived conversations back to the feed, and queue a move of their messages back to the user's INBOX. Takes a cluster_key and category exactly as list_feed reported them. The reply's result field says unarchived with how many came back, already_in_feed when the cluster was there but nothing in it was archived, or nothing_to_unarchive when the key and category matched no conversations at all. Whenever the cluster holds mail the feed would show, the moves are queued for all of it rather than only what was unarchived, since a thread a reply brought back sits in the feed with its mail still filed away.

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": {
      "cluster_key": "<cluster_key>",
      "category": "<category>"
    },
    "name": "unarchive_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesThe category list_feed reported for this cluster.
cluster_keyYesThe cluster key from list_feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the behavioral burden well: it discloses both feed restoration and queued INBOX moves, including that moves can cover all feed-visible mail rather than only newly unarchived items. It also documents the unarchived, already_in_feed, and nothing_to_unarchive outcomes, clarifying no-op and unmatched-input behavior.

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?

The description is front-loaded with the action and then logically covers inputs, results, and an important scope exception. The final sentence is long and somewhat convoluted, but its explanation of the broader queued-move behavior is substantive rather than filler.

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?

Despite having no annotations or output schema, the definition supplies the side effects, identifier source, result-field outcomes, and the non-obvious behavior for clusters already partly present in the feed. An agent has enough context to invoke it correctly and anticipate its effects.

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 already 100%, including the category enum and list_feed provenance, but the description adds that both values must be used exactly as reported. It also clarifies that the key and category are matched together against conversations, which adds useful invocation semantics beyond the 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 precisely states that the tool restores a cluster's archived conversations to the feed and queues their messages for movement to INBOX. Its cluster-wide scope and feed-restoration effect distinguish it from unarchive_conversation and archive_cluster.

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 gives clear operational context and instructs the agent to supply cluster_key and category exactly as reported by list_feed. It does not explicitly say when to prefer unarchive_conversation or other alternatives, so the guidance is strong but not exhaustive.

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