Skip to main content
Glama

Viral Manager

by com.viral-managers

update_folder

Idempotent

Update an assignment folder: ONE operation per call among rename, move to another parent, archive/unarchive (cascades to the whole subtree, unarchive also restores ancestors), or change the creator owner. Renaming keeps the subtree and all assignment links (never delete and recreate to rename).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderYesFolder to update (id, name or full path)
renameNoNew name. Empty = no rename.
archiveNoArchive or restore the folder and its subtreekeep
owner_modelNoNew creator owner (name, email, model_id) or 'none' to clear. Empty = unchanged.
move_to_parentNoNew parent folder (id, name or path), or 'root' to make it a root folder. Empty = no move.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as readOnly=false, idempotent=true, and destructive=false. The description adds valuable behavioral context beyond those hints: subtree cascading for archive/unarchive, ancestor restoration on unarchive, and preservation of assignment links during rename. There is no contradiction with 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 three sentences with no filler. It front-loads the most important constraint (one operation per call), then lists the supported operations, and ends with a specific warning that prevents a common misuse. Every sentence earns its place.

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 5-parameter mutation tool with a complete schema and useful annotations, the description covers the key edge behaviors: cascade scope, ancestor restoration, link preservation, and the single-operation limit. No aspect needed to call the tool correctly is missing, and the absence of an output schema is not a gap here.

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 description coverage is 100%, so the schema already documents each parameter. The description adds important operational semantics not present in the schema, such as 'ONE operation per call', cascade behavior for archive, ancestor restoration on unarchive, and the rename safety guarantee. This elevates it above the baseline 3.

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 identifies the tool as updating an assignment folder and enumerates the exact supported operations: rename, move, archive/unarchive, and change owner. This distinguishes it from siblings like archive_folder, move_folders, and delete_folder by spelling out the resource and the operation scope.

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?

The description gives concrete usage guidance: one operation per call, archive cascades, unarchive restores ancestors, and renaming preserves links rather than deleting and recreating. It does not explicitly compare against sibling tools like archive_folder or move_folders, but the operatation list plus the 'never delete and recreate' warning gives an agent enough context to choose appropriately.

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