Viral Manager

set_drive_folder

Idempotent

Link (or unlink with 'none') a Google Drive folder to ONE target: a production folder (its assignments and sub-folders inherit it) or a single assignment (takes precedence over its folder). The creator's next uploads for that target go straight into the Drive folder.

Input Schema

TableJSON Schema

Name	Required	Description
`drive_folder`	Yes	Drive folder id or name (see list_drive_folders / create_drive_folder), or 'none' to unlink
`assignment_id`	No	Target assignment id. Use this OR production_folder.
`production_folder`	No	Target production folder (id, name or full path). Use this OR assignment_id.

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: production-folder assignments and sub-folders inherit the link, assignment links take precedence, and only the creator's next uploads are routed to the Drive folder. It also clarifies the unlink behavior via 'none'. These side-effect semantics are valuable and not present in the structured data.

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?

Two sentences deliver the core purpose, target options, inheritance rules, and unlink behavior with no filler. The most important information is front-loaded, and every clause adds meaning.

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?

For a mutating tool with three parameters and no output schema, the description covers the main semantics: target selection, inheritance, precedence, and unlink. There is minor ambiguity about whether an unlink operation requires a target argument, but overall the definition provides enough context for an agent to use it correctly.

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?

The input schema already covers all parameters at 100%, so the baseline is 3. The description adds value by explaining the one-target constraint, the relationship between assignment_id and production_folder, and the special 'none' unlink value, which goes beyond the schema's property-level descriptions.

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 specific action: link a Google Drive folder to one target, and clearly names the two target types (production folder or assignment). This differentiates it from sibling tools like create_drive_folder and list_drive_folders by focus and behavior.

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 clear usage context: the tool links folders to exactly one target and explains the distinction between production-folder and assignment targets, including precedence. It does not explicitly enumerate alternative tools, but no sibling directly overlaps with this link/unlink behavior, so the guidance is sufficient.

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

All Viral Manager tools Inspect

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

Need Help?