filmcraft-edit

Overview Schema Source Related Servers Discussions Admin

run_command

Execute any FilmCraft engine command on a project to apply edits or operations, saving changes back unless save is set to false.

Instructions

Run any FilmCraft engine command on the project (times are ticks: 254016000000 per second, or {seconds: n}). Saved back unless save=false.

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": {
      "id": "<id>"
    },
    "name": "run_command"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`save`	No
`params`	No
`project`	No	Path to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds useful behavioral context: results are saved back unless save=false, and it specifies the tick/time-unit convention, but it does not describe failure behavior, validation, or side effects of arbitrary engine commands.

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 compact sentence with no filler, front-loading the action and then giving the two most important behavioral details (persistence and time units). Nothing is wasted.

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?

No output schema exists, so the description should carry more completeness burden. It covers persistence and time representation, but for a generic engine-command dispatcher with a nested free-form params object, it omits how to discover valid command ids and what errors or return values to expect; the list_commands sibling partially compensates but is not mentioned.

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 description coverage is only 25%, with only the project parameter documented. The description clarifies save semantics and the tick format for time parameters, but leaves the required id and the free-form params object largely undefined, which is a significant gap for a generic dispatcher.

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: 'Run any FilmCraft engine command on the project.' It makes clear this is a generic command-dispatch escape hatch rather than a named operation, though it does not explicitly distinguish itself from list_commands or run_batch.

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

Usage Guidelines2/5

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

No guidance on when to use this generic tool versus the many dedicated siblings (add_clip, trim_clip, apply_effect, etc.) or versus run_batch/list_commands. The only conditional guidance is save=false and time formatting, not tool selection.

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