Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_import

Import one or more media files by absolute path into a FilmCraft project so they are available for editing.

Instructions

Import one or more media files into the filmCraft project.

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": {
      "files": "<files>"
    },
    "name": "fc_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesAbsolute paths to the media files to import.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

C2.9/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 behavioral burden, yet it only implies mutation via the word 'Import'. It does not disclose whether files are copied into the project or referenced in place, what happens on duplicate or missing paths, whether the operation is reversible, or what the call returns.

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?

A single front-loaded sentence with no wasted wording; the action and target appear immediately. It is appropriately sized, though its brevity comes at the cost of the behavioral detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with zero annotation coverage and no output schema, the description is too thin: it omits side effects, error conditions, and any indication of what the agent should do with the result. It is complete only about the literal action, not about how to call it safely.

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 documents 'files' as an array of absolute paths with minItems 1. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 gives a specific verb (Import) and resource (one or more media files) into a named target (filmCraft project), which is unambiguous and clearly distinct from siblings like fc_export or fc_render_frame. It stops short of differentiating itself from adjacent tools such as fc_exec or fc_probe, which might also touch media files.

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?

There is no guidance on when to use this versus fc_exec, fc_probe, or fc_inspect, and no prerequisites are stated (e.g., whether the project must be open or initialized first). The agent is left to infer that importing is the correct first step before other operations.

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