Viral Manager

dispatch_video

Idempotent

Send a delivered video of an assignment (a creator rush, an editor reel or a clipper clip) to one or several crew members of a LATER step, or plan a variation before it is delivered. With video_id: that video goes to the recipients now. Without video_id: plans variation number variation (0 = next free) of from_stage; the next video that step delivers fills it and goes to those recipients. Recipients are notified by push. Get video ids from get_assignment (submitted_videos / crew_videos).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No	Optional instruction attached to this send (e.g. 'post at 6pm, caption B'), shown only to the recipients and managers. Sending again to a member who already has the video replaces the note.
`video_id`	No	Delivered video id to send. Empty = plan a variation instead.
`variation`	No	Variation number to plan (0 = next free one)
`from_stage`	No	Step whose video is expected (only used when planning, without video_id)	editor
`recipients`	Yes	Crew members by name or member_id (see list_crew). Order matters: creator -> editor/clipper/poster, editor -> clipper/poster, clipper -> poster.
`from_member`	No	Only when planning an editor/clipper variation: crew member (name or member_id) whose video fills it, so editor 1's reel goes to poster 1 and editor 2's to poster 2. Empty = the first video any member of that step delivers.
`assignment_id`	Yes	Assignment id (from list_assignments)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

addedInput schema / properties / from_member

Added value: +{
+  "default": "",
+  "description": "Only when planning an editor/clipper variation: crew member (name or member_id) whose video fills it, so editor 1's reel goes to poster 1 and editor 2's to poster 2. Empty = the first video any member of that step delivers.",
+  "type": "string"
+}

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / note

Added value: +{
+  "default": "",
+  "description": "Optional instruction attached to this send (e.g. 'post at 6pm, caption B'), shown only to the recipients and managers. Sending again to a member who already has the video replaces the note.",
+  "maxLength": 1000,
+  "type": "string"
+}

AddedSep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description discloses key behaviors: sending again replaces the note, recipients are notified by push, and the planning mechanism for variations. It also clarifies the meaning of from_member and from_stage in context, adding substantial value over the schema.

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 structured and efficient: it leads with the primary purpose, then details the two modes, and adds relevant context (notification, id source) without redundancy. Every sentence contributes to understanding, and the length is justified by the tool's complexity.

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?

Given the tool's complexity (7 parameters, two modes, no output schema), the description is complete. It explains the planning flow, recipient order, and prerequisite data source, and it does not leave critical ambiguities. The lack of an output schema is acceptable since return values are not needed for calling.

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 each parameter is individually documented. The description adds meaning by explaining the interplay between video_id and variation, the conditional use of from_stage, and the significance of recipient ordering. This goes beyond the schema, though it does not exhaustively elaborate every parameter.

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 tool's action ('Send a delivered video... to one or several crew members') and its resource (assignment video), and distinguishes two modes (send existing video vs. plan a variation). It differentiates from sibling tools like remove_dispatch by explicitly covering the dispatch/planning action.

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 explains when to use each mode (with or without video_id) and the ordering of recipients, and it references get_assignment for obtaining video ids. It does not explicitly name alternative tools or state when not to use this tool, but the dual-mode guidance is clear enough for most use cases.

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

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

Need Help?