Skip to main content
Glama

video_plan

Build a video timeline from captured screens with an intro, timed scenes, zooms, scroll speed-ups, captions and an outro; this replaces the current timeline.

Instructions

Build the video timeline from all captured screens: intro, one scene per screen with automatic timing, zooms, scroll speed-ups and captions, then an outro. Replaces the current timeline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "video_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNo
formatNo
appNameNo
taglineNo
targetSecondsNodesired total length

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 the important destructive fact that the existing timeline is replaced and describes the generated structure (automatic timing, zooms, scroll speed-ups, captions). It says nothing about required permissions, idempotency, or whether prior manual edits are lost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and followed by the replacement warning. Every clause adds information; no filler.

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?

A five-parameter mutation tool with no annotations and no output schema needs more: the four undocumented parameters and the consequence of replacing the timeline (reversibility, prerequisites) are unaddressed.

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 coverage is only 20% (just targetSeconds), so the description needed to compensate but mentions none of cta, format, appName, or tagline. 'Automatic timing' loosely relates to targetSeconds but adds no concrete meaning beyond the schema.

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?

States a specific verb and resource ('Build the video timeline') and enumerates what gets generated: intro, per-screen scenes, zooms, captions, outro. The agent can tell this is a timeline-construction step, though it is not explicitly distinguished from siblings like video_timeline or video_edit.

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?

'From all captured screens' implies a prerequisite and a usage context, and 'Replaces the current timeline' signals a caution. However, there is no explicit when-to-use versus video_timeline/video_edit/video_render, and no stated exclusions.

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