Skip to main content
Glama
DareDev256

fcpxml-mcp-server

by DareDev256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inspect

Read FCPXML timelines or projects without modifying them to review clips, markers, roles, effects, and pacing before editing.

Instructions

Read a timeline or project without changing it. Use this first to understand what you are working with. Actions: list_projects, analyze_timeline, analyze_pacing, list_clips, list_markers, list_roles, list_keywords, list_effects, list_templates, list_library_clips, list_compound_clips, list_connected_clips, filter_by_role, list_keyframes, list_speed_points.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoArguments for the chosen action, e.g. {"filepath": "/path/to/project.fcpxml"}. Any action that takes a filepath also accepts expected_sha256: the call refuses if the file no longer hashes to it (every write result and analyze_timeline report the current sha256).
actionYesWhich operation to run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.26.0
    • addedInput schema / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "action": {
+          "const": "list_keyframes"
+        }
+      },
+      "required": [
+        "action"
+      ]
+    },
+    "then": {
+      "properties": {
+        "args": {
+          "additionalProperties": false,
+          "properties": {
+            "clip_path": {
+              "description": "Exact clip_path returned by inspect.list_keyframes; never a clip name.",
+              "type": "string"
+            },
+            "filepath": {
+              "description": "Input FCPXML or .fcpxmld bundle.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "filepath"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "args"
+      ]
+    }
+  },
+  {
+    "if": {
+      "properties": {
+        "action": {
+          "const": "list_speed_points"
+        }
+      },
+      "required": [
+        "action"
+      ]
+    },
+    "then": {
+      "properties": {
+        "args": {
+          "additionalProperties": false,
+          "properties": {
+            "clip_path": {
+              "description": "Exact clip_path returned by inspect.list_keyframes; never a clip name.",
+              "type": "string"
+            },
+            "filepath": {
+              "description": "Input FCPXML or .fcpxmld bundle.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "filepath"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "args"
+      ]
+    }
+  }
+]
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list_projects",
-  "analyze_timeline",
-  "analyze_pacing",
-  "list_clips",
-  "list_markers",
-  "list_roles",
-  "list_keywords",
-  "list_effects",
-  "list_templates",
-  "list_library_clips",
-  "list_compound_clips",
-  "list_connected_clips",
-  "filter_by_role"
-]New value: +[
+  "list_projects",
+  "analyze_timeline",
+  "analyze_pacing",
+  "list_clips",
+  "list_markers",
+  "list_roles",
+  "list_keywords",
+  "list_effects",
+  "list_templates",
+  "list_library_clips",
+  "list_compound_clips",
+  "list_connected_clips",
+  "filter_by_role",
+  "list_keyframes",
+  "list_speed_points"
+]
    • changedInput schema / properties / args / description
      Previous value: -"Arguments for the chosen action, e.g. {\"filepath\": \"/path/to/project.fcpxml\"}."New value: +"Arguments for the chosen action, e.g. {\"filepath\": \"/path/to/project.fcpxml\"}. Any action that takes a filepath also accepts expected_sha256: the call refuses if the file no longer hashes to it (every write result and analyze_timeline report the current sha256)."
  2. Addedv0.22.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the most important trait: this is a non-mutating read operation. It says nothing about permissions, supported input formats beyond the schema's own field notes, or failure modes for missing/corrupt files, so the reporting is only partial.

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?

Two short sentences followed by a flat action list, with the read-only constraint and the 'use first' directive front-loaded before the enumeration. The list is long but functional; no sentence is filler, though the trailing list lacks any grouping or ordering rationale.

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?

For a 15-action dispatcher with no annotations and no output schema, the description covers the essentials (read-only, when to reach for it, available operations) but not the payoff: it never indicates what any action returns, nor references the expected_sha256 staleness check that guards against acting on an outdated file.

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 filepath, clip_path, args, and the expected_sha256 guard are already documented in the schema, including the versioning safeguard. The description adds nothing about parameter meaning beyond restating the action names, so the baseline 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?

States a specific verb and resource ('Read a timeline or project') and adds the key scoping constraint 'without changing it', which cleanly separates it from mutating siblings like edit, mark, generate, and deliver. It enumerates all 15 actions, though it does not explain what each action does, so an agent still has to infer what analyze_pacing vs. analyze_timeline return.

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?

'Use this first to understand what you are working with' gives a clear sequencing heuristic for entering an unfamiliar file. However, it names no alternative (find, view, scenes, transcript) and gives no guidance on when NOT to use it or how to choose among the 15 listed actions, leaving the hardest selection decision to inference.

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