Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

plan_structure

Plan a long-form video's segment structure—hook, intro, chapters, outro—for a target duration and get time ranges plus retention advice; nothing is saved.

Instructions

Plan the segment structure (hook, intro, chapters, outro) of a long-form video for a target duration. Returns time ranges and retention advice. Does not save anything.

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": {
      "minutes": "<minutes>"
    },
    "name": "plan_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesYesTarget video length in minutes
chaptersNoNumber of chapters; auto if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it declares the tool is pure computation with no persistence ('Does not save anything') and discloses the shape of the response (time ranges and retention advice). It omits any permission, cost, or determinism notes, but for a side-effect-free planner those are minor.

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?

Three short sentences, front-loaded with the purpose, then the return value, then the boundary condition. No filler or repetition.

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

Completeness4/5

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

For a two-parameter, non-destructive planning tool with full schema coverage, the definition covers purpose, inputs, rough output, and the no-save caveat. Without an output schema the description could say more about the exact form of the returned time ranges, but nothing essential to calling it is missing.

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 description coverage is 100%, so 'minutes' and 'chapters' (including the auto-if-omitted default) are already documented in the schema. The phrase 'for a target duration' echoes the minutes parameter but adds no format or constraint detail beyond what is structured.

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?

States a specific verb (plan) and resource (segment structure) and enumerates the components produced: hook, intro, chapters, outro. The final sentence 'Does not save anything' draws a clear boundary against the sibling save/create tools without needing to open their schemas.

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?

Clear context for use: a long-form video with a target duration, and an explicit non-goal (it does not persist). It stops short of naming an alternative such as generate_timestamps or analyze_script, so the agent must infer which planning-adjacent sibling to pick in a given situation.

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