Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

shot_list

Split a narration script into timed visual beats with timecodes, so a long video never stays on one static shot.

Instructions

Split a narration script into visual beats (a new visual every N seconds) with timecodes, so a long video never stays on one static shot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script": "<script>"
    },
    "name": "shot_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpmNo
scriptYes
seconds_per_visualNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral load, and it does disclose the core rule (a new visual every N seconds) and that output carries timecodes. It leaves open whether the split is deterministic, how it handles sentence boundaries, and what the returned structure looks like — gaps that matter for a tool with zero annotation coverage.

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?

A single front-loaded sentence with action first, mechanism second, and rationale last. Nothing is repeated or padded.

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

Completeness2/5

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

For a tool with three undocumented parameters, no annotations, and no output schema, the description should explain wpm and the shape of the returned beats/timecodes. It covers roughly half of what an agent needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all three parameters. It indirectly conveys seconds_per_visual via "every N seconds" and script via "narration script," but wpm — the parameter that governs timing estimation — is never mentioned or explained anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Split a narration script into visual beats ... with timecodes" gives a specific verb and resource, plus the delivered artifact (visual beats with timecodes). It is clear what the tool produces, though it does not explicitly distinguish itself from near-siblings like generate_timestamps or analyze_script.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only hint of when to use it is the trailing rationale "so a long video never stays on one static shot," which implies a long-video scenario but never states preconditions, exclusions, or which sibling to pick instead. An agent gets no routing guidance against generate_timestamps or plan_structure.

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