FilmoraMCP-Server

by SkieAdmin

Overview Schema Source Related Servers Discussions Admin

Python

Local

filmora_snapshot_frame

Destructive

Save a source or player frame in Filmora via its Snapshot command to capture a still image, not a UI screenshot.

Instructions

Ask Filmora to save a source/player frame via its Snapshot command (different from UI screenshot).

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_snapshot_frame"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a non-read, state-changing call. The description adds the Snapshot-vs-screenshot distinction but says nothing about where the file lands, its format, or whether an existing file would be overwritten — the behavioral detail most relevant to a destructive-hinted save.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a parenthetical that earns its place by pre-empting confusion with the screenshot tool. No filler, no restatement of the tool name.

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 zero-parameter, no-output-schema tool this covers the core action and the sibling disambiguation, but it omits what 'source/player' refers to and what state (playhead position, loaded media) is required for the snapshot to be meaningful, which an agent needs to sequence it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and schema description coverage is 100%, so there is nothing for the description to compensate for. Baseline 4 applies; no parameter semantics are missing.

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

Purpose5/5

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

States a specific verb and resource ('save a source/player frame') and names the mechanism ('via its Snapshot command'). It explicitly differentiates itself from the filmora_screenshot sibling, so an agent can pick the right tool without opening either schema.

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?

The parenthetical 'different from UI screenshot' gives implicit routing guidance against the closest sibling, but there is no explicit when-to-use condition, no preconditions (e.g. a source/player must be loaded or a frame positioned), and no mention of what to do instead for a UI capture.

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