Skip to main content
Glama

Viral Manager

by com.viral-managers

archive_my_accounts

Idempotent

Archive (or restore) one or SEVERAL of the org's own connected accounts (My Accounts). Archiving takes them out of the lists and stops their sync WITHOUT deleting anything, and it can be undone: prefer it to delete_my_accounts whenever the data might still be wanted. Restoring takes a plan slot back, so it can fail with LIMIT_REACHED.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountsYesAccounts to archive or restore (username, display name or id from list_my_accounts)
archivedNotrue = archive, false = restore into the active list
platformNoDisambiguates when the same username exists on both platformsall

TDQS

A4.7/5.0
Behavior5/5

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

The description substantially exceeds what the annotations alone provide. It discloses that archiving removes accounts from lists, stops sync, does not delete anything, is undoable, and that restoring consumes a plan slot and can fail. These details are not captured by readOnlyHint=false, idempotentHint=true, or destructiveHint=false, and nothing contradicts the annotations.

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?

The description is compact and front-loaded: the first sentence states the main purpose, and each subsequent sentence adds distinct operational value such as side effects, reversibility, and failure mode. There is no filler or unnecessary repetition of schema fields.

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 mutating tool with no output schema, this description is highly complete. It covers what the operation does, what side effects occur, reversibility, the main failure condition, and how to select this tool over its destructive sibling. An agent has enough information to invoke it 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 description coverage is 100%, so the schema already documents the accounts, archived, and platform parameters well. The description adds useful conceptual context about the archive/restore mental model and plan-slot cost, but it does not add new per-parameter format or syntax details 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 clearly states the operation: archiving or restoring one or more of the org's own connected accounts. It also explicitly differentiates itself from delete_my_accounts by emphasizing that archiving is reversible and non-destructive, which distinguishes it from sibling tools.

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?

The description explicitly says to prefer this tool over delete_my_accounts whenever data might still be wanted, which is a concrete selection rule. It also warns about a real failure mode when restoring, LIMIT_REACHED, giving the agent useful expectations about when the operation can fail.

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

All Viral Manager toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool has a distinct target resource/action, and the descriptions are unusually explicit about differences (e.g., 'Distinct from the watchlist', 'Separate list from list_tags'). A few pairs are still easy to confuse without careful reading: delete_folder vs delete_folders differ only by singular/plural, and the three download-URL tools (get_post_download_url, get_asset_download_url, get_my_account_post_download_url) plus the category/tag families require attention to pick correctly.

Naming Consistency4/5

The snake_case verb_noun pattern is followed consistently throughout (list_*, get_*, create_*, update_*, delete_*, set_*, tag_*). Minor deviations: archive_folder and archive_my_accounts also perform restore despite their names, delete_folder/delete_folders split one operation by cardinality, and tag_posts/tag_my_account use a different verb style than the set_* family for metadata mutations.

Tool Count2/5

At 56 tools, this far exceeds the 25+ threshold for 'too many,' even though the server spans multiple subdomains (watchlist, analysis, assignments, folders, my accounts, assets, Drive, categories/tags). Obvious consolidation candidates exist — delete_folder/delete_folders, the three download-URL getters, and the parallel list_my_account_* listers — and the sheer surface is heavy for an agent to navigate.

Completeness4/5

Core workflows are thoroughly covered with no dead ends: watchlist → analyze → assign → folder → track → approve has full lifecycle support, including reversible archive vs permanent delete choices. Minor gaps exist but are work-aroundable: no create/update for my accounts or models (app-side OAuth/admin only), no way to delete a viral post or a post note, and asset upload only happens in the app.

Resources