Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

production_checklist

Returns a stage-by-stage checklist for long-form video projects, covering pre-production, recording, editing, and publishing to keep each phase on track.

Instructions

Return a stage-by-stage production checklist for a long-form video (pre-production, recording, editing, publishing).

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": "production_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoall

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?

No annotations are supplied, so the description carries the full burden. It discloses the output shape (stage-by-stage checklist across four phases) and implies a read-only retrieval, but says nothing about whether the checklist is static or project-specific, or whether results vary by any context.

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 no filler; the parenthetical stage list adds useful scope without waste.

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 one-parameter read tool with no output schema, the description covers what is returned but omits any treatment of the optional stage filter and its default. It is adequate to call with no arguments but incomplete for the parameterized case.

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 0%, so the description should compensate for the single 'stage' parameter. It lists the four stages that correspond to the enum values, which helps, but never states that a stage filter exists, that 'all' is a valid value, or that it defaults to all — leaving the actual filtering behavior to be inferred from 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?

The description uses a specific verb and resource ('Return a stage-by-stage production checklist') and scopes it to long-form video, enumerating the four stages covered. It does not explicitly contrast with siblings like plan_structure or shot_list, but the purpose is unambiguous on its own.

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: an agent can infer this is for getting a checklist rather than generating a plan or analyzing a script, but there is no explicit when-to-use statement, no exclusions, and no mention of how it relates to the plan_structure or shot_list siblings.

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