Busymail

Archive a conversation

archive_conversation

Archive one conversation out of the feed. THIS MOVES REAL MAIL: as well as marking the thread archived in Busymail, it queues a move of every message in it out of the user's INBOX and into the account's archive folder, so the change shows up in Apple Mail or whatever else they use. It also drops any pin resting on the thread, and the pin on its cluster if this empties it. The reply's result field says archived, or already_archived when it was already out of the feed; messages_queued_to_move counts the messages queued, which is not zero even for already_archived, since a message left behind by an earlier failure still gets moved. Prefer asking the user before archiving mail they have not mentioned.

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": "archive_conversation"
  }
}

Input Schema

Name	Required	Description	Default
`conversation_id`	Yes	The conversation's UUID, from list_feed, get_cluster or search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations to lean on, the description carries the full burden and does so: it discloses that real mail is moved out of INBOX into the archive folder (visible in other clients), that pins on the thread and possibly its cluster are dropped, and it explains the result field values 'archived' vs 'already_archived' plus why messages_queued_to_move can be non-zero even for already_archived.

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 critical side-effect warning is front-loaded in caps and every sentence conveys operational information, though the messages_queued_to_move explanation is dense and slightly convoluted in a single sentence.

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 one-parameter mutation with no output schema, the description covers the side effects, pin cascades, and return-field semantics, leaving nothing an agent needs in order to call it safely.

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 single parameter is fully documented in the schema itself (UUID sourced from list_feed, get_cluster or search), so the description adds no meaning beyond it; baseline 3 applies.

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?

States a specific verb and resource ('Archive one conversation out of the feed') and the word 'one' scopes it against the sibling archive_cluster, so an agent can pick the right tool without opening either schema.

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 closing line gives a genuine usage constraint — ask the user before archiving mail they have not mentioned — but there is no explicit routing to alternatives such as archive_cluster for whole clusters or unarchive_conversation for reversal; that comparison is only implied by the 'one conversation' scope.

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

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