Skip to main content
Glama

write_statonic_project

Create JSON project files for the Statonic video editor to structure video content with text overlays and track segments.

Instructions

Write a Statonic project JSON file.

TEXT STYLING & POSITIONING RULES (follow these automatically):

  1. Font size: 75-100px (use 85-90 for multi-line text, adjust based on text length)

  2. Break text into 2-3 lines using \n to prevent going off screen

  3. Position: y = 0.25 to 0.31 (lower middle of top half), x = 0 (centered)

  4. Coordinate system: x=0,y=0 is center; y=1 is top; y=-1 is bottom

  5. After creating project, use render_preview to verify text doesn't block subjects

  6. If blocking subject's face/upper body, adjust y down to 0.22-0.25

HOOK FORMULA EXAMPLES (proven high-performance):

  • "how to [VERB] so fast it feels illegal" (CAPS on key verb, e.g. "how to LEARN\nso fast it\nfeels illegal")

  • "99% of [audience] do X the WRONG way" (specific number creates credibility)

  • "the [topic] trick nobody talks about"

  • 2-3 lines, 4-7 words each — NOT one long sentence

  • Use CAPS for ONE emphasis word per line, not the whole text

  • Use generate_hook_options tool to get 5 high-quality hook variants before writing

Example text formatting:

  • "how to study chemistry" → "how to study\nchemistry and get\n99/100" (fontSize: 90)

  • "ACTIVE RECALL 🤫" → single line is fine (fontSize: 75-100)

IMPORTANT: VideoSegment requires: src (not sourceFilePath), name, fileDurationUs, sourceWidth, sourceHeight. Track requires: label. See example:

{ "name": "My Video", "canvas": {"width": 1080, "height": 1920}, "tracks": [ { "id": "track-1", "label": "Base", "type": "video", "segments": [{ "id": "seg-1", "type": "video", "src": "/path/to/video.mp4", "name": "clip-name", "startUs": 0, "durationUs": 4200000, "sourceStartUs": 0, "sourceDurationUs": 4200000, "fileDurationUs": 5000000, "sourceWidth": 1080, "sourceHeight": 1920, "clipX": 0, "clipY": 0, "clipScale": 1, "cropLeft": 0, "cropRight": 0, "cropTop": 0, "cropBottom": 0 }] }, { "id": "track-2", "label": "Text", "type": "text", "segments": [{ "id": "text-1", "type": "text", "text": "Hello", "startUs": 0, "durationUs": 2000000, "x": 0, "y": 0, "fontSize": 80, "color": "#ffffff", "fontFamily": "Arial" }] } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesComplete Statonic project JSON
filenameYesOutput filename (e.g., "biology-study-video.json")
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior by detailing the output (a JSON file), formatting rules, and post-actions (e.g., using render_preview). However, it lacks explicit mention of potential side effects like file overwriting or error handling, which slightly limits transparency.

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

Conciseness2/5

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

The description is overly verbose and poorly structured, mixing tool purpose with extensive styling rules, hook formulas, and examples that belong in external documentation. It spans multiple sections without clear separation, making it difficult to quickly grasp the core functionality, though the initial sentence is front-loaded.

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?

Given the complexity of creating a Statonic project with nested objects and no output schema, the description is mostly complete. It includes detailed examples, formatting rules, and integration with other tools (e.g., render_preview), but it could benefit from clarifying error cases or validation requirements for the JSON input.

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 the schema already documents both parameters ('project' and 'filename'). The description adds context by providing an example JSON structure for the 'project' parameter and naming conventions for 'filename', but this is marginal value beyond the schema's baseline documentation.

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?

The description clearly states the verb 'Write' and the resource 'Statonic project JSON file', making the purpose specific and actionable. It distinguishes from siblings like 'read_project' (which reads) and 'render_preview' (which renders), establishing a unique write operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance, including when to use it (e.g., 'After creating project, use render_preview to verify text doesn't block subjects') and alternatives (e.g., 'Use generate_hook_options tool to get 5 high-quality hook variants before writing'). It also specifies prerequisites like following styling rules and hook formulas.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dnldsz/StatonicMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server