Skip to main content
Glama
Sign In
FilmoraMCP-Server

FilmoraMCP-Server

by SkieAdmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

filmora_marker

Destructive

Add, edit, or color-code timeline markers and set, clear, or adjust in/out points in Filmora's focused timeline or player.

Instructions

Add/edit marker, assign color mark, or control in/out range in the focused timeline/player.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "filmora_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoadd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, lowering the bar, but the description never discloses which action is destructive (clear_in_out removes in/out marks) or what happens to existing markers on edit. It only adds the scoping phrase 'focused timeline/player'.

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 efficient sentence with the core verb front-loaded and no filler. The action list is slightly run-on but each clause carries distinct information.

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 one-parameter, no-output-schema tool this is minimally adequate, but an agent still cannot tell when the tool applies versus general edit/playback tools, or what the destructive clear_in_out action wipes out.

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 coverage is 0%, so the description must carry the load. It does group the 13 bare enum values into meaningful categories (add/edit, color assignment, in/out range control), which adds real meaning beyond the raw enum list, but it never explains defaults, combinations, or per-value effects.

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 specific verbs (add/edit marker, assign color, control in/out range) and the resource/scope (focused timeline/player). No sibling tool handles markers, so the function is distinguishable, though it doesn't explicitly contrast with filmora_edit or filmora_playback.

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 choose this tool over alternatives, nor any exclusions. The only contextual hint is 'focused timeline/player', which implies a prerequisite but is not framed as one.

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