Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

save_script

Save or replace a segment's narration script, then compare its estimated speaking time against the planned duration.

Instructions

Save (or replace) the narration script of one segment and report its estimated speaking time versus the planned time.

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": {
      "project": "<project>",
      "order": "<order>",
      "script": "<script>"
    },
    "name": "save_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
scriptYesNarration text for this segment
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose that existing script content is replaced and that a time comparison is returned, which is meaningful behavioral context. It omits permission requirements, validation behavior (e.g., empty or overlong scripts), and whether replacement is recoverable.

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 sentence with the write action front-loaded and the return-value note trailing. No filler, no repetition of the tool name's meaning.

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?

Because there is no output schema, the description's mention of the speaking-time-vs-planned-time report is valuable and necessary. Still, for an unannotated mutation tool with a third of its parameters undocumented, an agent lacks guidance on failure modes and on the 'project' argument.

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

Parameters3/5

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

Schema coverage is 33% — only 'script' is documented in the schema. The description clarifies that the script is narration text for a single segment and that the segment is identified via 'order', but it says nothing about the 'project' parameter or that 'order' is 1-based.

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 names a specific verb (save/replace) and resource (narration script of one segment) and adds a secondary effect (speaking-time estimate vs. planned time). It does not explicitly differentiate itself from the sibling analyze_script, so an agent must infer that this one writes while that one likely evaluates.

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

Usage Guidelines3/5

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

The parenthetical '(or replace)' implies upsert semantics for an existing segment script, which is useful usage context. However, there is no explicit statement of when to use this versus analyze_script or how to handle a segment that does not yet exist.

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