Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

create_project

Creates and saves a long-video project with an auto-generated structure and returns its project name for use in other tools.

Instructions

Create and save a long-video project with an auto-generated structure. Use the returned project name in other tools.

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": {
      "title": "<title>",
      "topic": "<topic>",
      "minutes": "<minutes>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
wpmNoNarration speed in words per minute
titleYesWorking title of the video
topicYesWhat the video is about
minutesYesTarget length in minutes
audienceNoWho the video is forgeneral audience
chaptersNo

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 supplied, the description carries the full burden and does disclose two meaningful behaviors: the call persists a project ("save") and it auto-generates a structure beyond what the caller supplies, and it reveals a return value (the project name). It says nothing about whether creation is reversible, whether duplicate titles collide, what permissions or quota apply, or what the generated structure actually contains.

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, both of which earn their place: the first defines the operation and its side effect, the second tells the agent what to do with the result. Front-loaded with no filler.

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 6-parameter creation tool with no annotations and no output schema, the definition covers the essentials — what is created, that a structure is generated, and that a project name comes back — which is why the missing output schema is tolerable. It stops short of describing the generated artifact, persistence/duplication semantics, or failure modes expected of a write operation.

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 83%, so the schema already explains most inputs (wpm, title, topic, minutes, audience) and the description does not need to repeat them. The one genuinely ambiguous parameter, chapters, is undocumented in the description even though "auto-generated structure" hints it may be optional or overridden — a missed opportunity, but the high coverage keeps this at baseline.

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 pairs a specific verb and resource ("Create and save a long-video project") with a distinctive side effect ("auto-generated structure"), so an agent knows this is a persistent creation tool, not a planning or listing one. It does not explicitly contrast with siblings like plan_structure or save_script, which would be needed for 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?

The second sentence gives useful downstream guidance: the returned project name is the handle other tools expect, implying this should be called early in a workflow. There is no statement of when not to use it, no prerequisites, and no named alternative for agents who only want to plan a structure without creating a project.

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