Skip to main content
Glama

Viral Manager

by com.viral-managers

update_asset

Idempotent

Update an asset of the library: rename it, set its internal notes, assign a category ('none' to clear), and add/remove custom tags. Several operations can be combined in one call. The '@model' tag is system-managed and cannot be edited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesAsset to update (id from search_assets, or exact name)
notesNoNew internal notes (replaces existing notes), or 'clear' to erase them. Empty = unchanged.
renameNoNew name. Empty = no rename.
add_tagsNoTags to add
categoryNoCategory (id or name), or 'none' to clear. Empty = unchanged.
remove_tagsNoTags to remove

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds genuine behavioral context: multiple operations can be combined in one call, and the '@model' tag is protected. It does not contradict the annotations, and it appropriately warns about a constraint that annotations cannot express.

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?

Three short, front-loaded sentences cover the main purpose, the multi-operation behavior, and a key constraint. There is no filler or repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description, fully documented schema, and annotations together provide enough for correct invocation: operations, combinability, clear/unchanged semantics, and the protected system tag. The only minor gaps are the lack of explicit return behavior and no direct guidance on when not to use this tool relative to siblings.

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 baseline is 3, but the description adds parameter-relevant meaning: it explains that operations can be combined and warns that '@model' cannot be passed for tag edits. This goes beyond the raw schema and helps an agent avoid a common failure.

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 opens with a concrete verb and resource ('Update an asset of the library') and enumerates the supported operations: rename, set internal notes, assign a category, and add/remove custom tags. This is specific enough to distinguish it from the many sibling update_* and tag-related tools without needing the 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 description clearly scopes what the tool is for by listing asset fields it can modify, and it adds an important exclusion: the '@model' tag is system-managed and cannot be edited. However, it does not explicitly say when to prefer this tool over alternatives such as tag_posts, set_post_category, or update_category, so usage context is implied rather than stated.

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