Skip to main content
Glama

add_marker

Add a sequence marker at a specified time in a FilmCraft project to flag key edit points, with optional name, color, comment, and duration.

Instructions

Add a sequence marker.

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": {
      "time": "<time>"
    },
    "name": "add_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
timeYesMarker time, in seconds
colorNoLabel name ("green") or "#rrggbb"
commentNo
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app
durationFramesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent knows this mutates local state, but the description adds nothing beyond that baseline. It does not say whether the marker is persisted immediately or only on save_project, nor how markers relate to the sequence being edited. For a write tool with six parameters, this leaves the behavioral picture thin.

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?

It is a single short sentence with no padding, but that brevity comes from under-specification rather than efficiency. There is nothing front-loaded beyond the bare verb and noun, so a reader gains almost nothing.

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?

A six-parameter mutation tool with no output schema and 50% schema coverage needs a description that explains defaults, persistence timing, and the meaning of the unlabeled fields. None of that is present, so an agent cannot confidently call this without inspecting the schema and guessing.

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 sits at 50%: time, color, and project are documented in the schema, while name, comment, and durationFrames are undocumented in both places. The description contributes zero parameter meaning, so the remaining coverage gap is completely unmitigated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Add a sequence marker" names a specific verb and resource, which distinguishes it from siblings like add_clip or add_text by the object being created. However, it never explains what a marker is in this domain (a timeline/sequence annotation) or what it is attached to, so the agent is inferring the resource from the surrounding toolset rather than from the description.

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 when-to-use guidance at all: no mention of when a marker is preferable to a clip, text, or transition, no prerequisites, and no note that the target project defaults to the connected app. The agent must infer usage purely from the tool name.

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