Skip to main content
Glama

Create long-form project

create_project

Start a long-form video project (YouTube tutorials, walkthroughs, lessons: up to 20 minutes finished, 1080p). Free. brand_id is an id or a kit's name. scenes sets up a scripted video in one call: each scene's script is what the recorder's teleprompter shows (the words to say, not stage directions). Every scene is checked first, so a bad one makes nothing. Returns the project as get_project does.

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

Input Schema

NameRequiredDescriptionDefault
titleYes
scenesNoThe video's scenes in order, each with a title and its script: the words the teleprompter shows while the person records: what to say, not stage directions.
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent, non-open-world write. Beyond that the description adds real value: the operation is free, and all-or-nothing ('every scene is checked first, so a bad one makes nothing'), plus what a successful call returns. It does not say whether rendering starts automatically or what that costs later.

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?

Information is front-loaded: form factor and limits first, then cost, then parameter meaning, then behavior, then return value. Sentences are dense with parentheticals but nearly every clause carries new information; the repeated teleprompter clarification in both prose and schema is slight redundancy.

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?

With no output schema, the line 'Returns the project as get_project does' usefully redirects the agent to a sibling for the response shape. Combined with cost, validation behavior, and parameter meaning, this is close to complete for a 3-parameter create tool; only render/cost follow-on behavior is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description still explains that brand_id can be an id or a kit's name and pulls in colors, fonts, logo, and default copy, and it clarifies that a scene's script is spoken text for the teleprompter rather than stage directions. Only title receives no elaboration, which is self-evident.

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 opens with a specific verb and resource ('Start a long-form video project') and immediately bounds it with concrete scope: YouTube tutorials, walkthroughs, lessons, up to 20 minutes finished, 1080p. That sets it apart from render/short-oriented siblings without naming them, though it never explicitly contrasts with a short-form project tool.

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?

It gives an implicit when-to-use rule: scenes 'sets up a scripted video in one call', implying a batch alternative to per-scene tools like add_scene. But there is no explicit when-not guidance, no mention of what to do when scenes are omitted, and no stated alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources