Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

analyze_script

Analyzes narration text to count words, estimate speaking duration at a set WPM, and flag pacing issues from very long sentences or paragraphs.

Instructions

Analyze any narration text: word count, estimated duration, and pacing warnings (very long sentences or paragraphs).

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": {
      "text": "<text>"
    },
    "name": "analyze_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpmNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the computed outputs and the pacing-warning criteria, which implies a non-mutating read-only analysis. However, it never states that nothing is persisted, how duration is estimated, or that the wpm assumption drives the estimate.

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 the verb and resource first and the concrete deliverables after the colon; every clause carries information and there is no filler.

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

Completeness3/5

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

For a simple two-parameter analysis tool with no output schema, the description adequately explains the returned metrics. It is incomplete on the one meaningful input knob (wpm) and on the absence of side effects, which matters given there are no annotations to cover them.

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% for two parameters, so the description must compensate, yet it never mentions the 'wpm' parameter (80-220, default 150) that determines estimated duration, nor any constraint on 'text'. Only an indirect hint ('estimated duration') gestures at wpm.

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?

The description gives a specific verb (analyze) and resource (narration text) and enumerates the outputs: word count, estimated duration, and pacing warnings for long sentences or paragraphs. An agent can tell exactly what it gets back, though it does not explicitly contrast itself with siblings such as save_script or generate_timestamps.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions; 'Analyze any narration text' only loosely implies it is a pre-flight check on a script. Usage must be inferred entirely from the output list.

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