Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_exec

Executes any FilmCraft command by its command ID, passing parameters as key-value pairs; use fc_list_commands to discover valid command IDs.

Instructions

Execute any filmCraft command by its command ID. Use fc_list_commands to discover IDs. Params are passed as key-value pairs.

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

Input Schema

NameRequiredDescriptionDefault
idYesfilmCraft command ID, e.g. timeline.razor, file.newBin.
paramsNoCommand parameters as a JSON object. Keys and types depend on the command.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

B3.3/5.0
Behavior2/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 does not disclose that arbitrary commands can mutate or destroy project state, whether operations are undoable, how errors for unknown command IDs surface, or whether any permission/context requirements exist — significant omissions for an unbounded command dispatcher.

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?

Three short sentences, front-loaded with the core action and ID-discovery step. The final sentence about key-value pairs is largely redundant with the schema and is the only expendable line.

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?

For a two-parameter dispatcher with no output schema or annotations, the description could say more about return values and mutation risk. It still omits where to look up valid params per command and what the call returns, leaving real gaps for an unbounded executor.

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% and the schema already explains that keys and types depend on the command, so the description's 'params are passed as key-value pairs' adds little. It misses the genuinely valuable pointer that per-command parameter details are obtainable via fc_inspect/fc_describe.

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: execute a filmCraft command addressed by command ID, and names fc_list_commands as the ID discovery path. It is clear what the tool does, though as a generic dispatcher it does not contrast itself with dedicated siblings like fc_import, fc_export, or fc_render_frame.

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?

Gives one concrete workflow hint (use fc_list_commands to discover IDs), which is genuinely useful. It never says when to prefer this generic executor over the specialized sibling tools or what preconditions (open project, valid context) must hold, so usage is only partially guided.

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

Deploy Server

Other Tools