Skip to main content
Glama

Viral Manager

by com.viral-managers
OverviewDiscussionsAdmin

list_folders

Read-only

List the organization's assignment folders as a tree (id, full path, creator owner, archived flag), each with the crew working in it (editors, clippers, posters attached to the posts it holds) and how many posts it holds. Folders organize the Production workflow; per-creator root folders drive automatic routing in the app. A folder has no crew owner of its own: a crew member sees a folder because posts inside are attached to them, so use crew to list someone's folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crewNoOnly folders holding at least one post attached to this crew member (name or member_id, see list_crew). Empty = all folders.
include_archivedNoAlso return archived folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / crew
      Added value: +{
+  "default": "",
+  "description": "Only folders holding at least one post attached to this crew member (name or member_id, see list_crew). Empty = all folders.",
+  "type": "string"
+}
  2. First observed

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, and the description adds meaningful behavior: a folder has no crew owner, visibility is mediated through posts, and the result includes nested crew members and post counts. This goes beyond the simple readOnly annotation and explains the access model.

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 dense sentences deliver purpose, domain context, and a selection rule without any filler. The most important behavior is front-loaded and every sentence adds information the agent needs.

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?

With no output schema, the description carries the return-format burden and explicitly names tree structure, key identifiers, creator, archive flag, associated crew, and post count. Given the small parameter set and readOnly annotation, no essentials are missing.

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 coverage is 100%, so the baseline is 3. The description adds valuable semantics for `crew`, explaining why the parameter exists and how folder membership is determined, and clarifies how `include_archived` fits into the output ('archived flag').

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?

Description opens with 'List the organization's assignment folders as a tree', naming the specific verb, resource, and output structure. It clearly distinguishes assignment folders from related siblings like list_drive_folders and list_assignments by specifying crew and post context.

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?

Provides clear context for use: folders are per-owner containers and crew visibility is driven by post attachments. It also gives explicit guidance to use the `crew` parameter to list a specific person's folders, though it does not name excluded alternatives.

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
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