Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

generate_timestamps

Generate YouTube chapter timestamps for a video project using actual script lengths when available, or planned segment times otherwise.

Instructions

Generate YouTube chapter timestamps for a project. Uses actual script lengths when available, otherwise planned times.

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>"
    },
    "name": "generate_timestamps"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
use_script_lengthsNoCompute times from saved scripts when present

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, and it does disclose one real behavioral trait: times come from saved scripts when they exist, falling back to planned times otherwise. It leaves open what happens when neither source exists, whether timestamps are persisted to the project or returned only, and whether repeated calls are idempotent. Those are material gaps 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?

Two short sentences with zero filler; the core action is front-loaded and the fallback condition follows immediately. Nothing could be cut without losing information.

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 tool this is close, but with no output schema the description should say what comes back — a formatted timestamp block, a list of chapter markers, or something written into the project. It also omits behavior when no script and no plan exist. Adequate but not complete for an agent that needs to know what to do with the result.

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 50%: the optional `use_script_lengths` flag is already documented in the schema, and the description's "actual script lengths when available" mostly restates that default. The required `project` parameter is undocumented in both places, and the description only implies it identifies the project, adding no format or lookup detail. Baseline 3 is appropriate given partial compensation for the coverage gap.

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 and artifact: "Generate YouTube chapter timestamps for a project." That is unambiguous and no sibling (analyze_script, plan_structure, production_checklist) produces timestamps, so the agent can distinguish it by resource alone. It stops short of an explicit contrast with any sibling, which keeps it from a 5.

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?

Usage is only implied by the purpose statement; there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. The one piece of routing logic given — "Uses actual script lengths when available, otherwise planned times" — describes internal fallback behavior rather than telling the agent when to pick this tool. An agent can infer the use case, but nothing is spelled out.

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