Skip to main content
Glama

filmcraft_auto_reframe_vertical

Converts horizontal 16:9 footage into 9:16 vertical video by tracking a chosen subject, keeping it centered for YouTube Shorts and TikTok.

Instructions

Converts horizontal 16:9 footage into 9:16 vertical video for YouTube Shorts/TikTok by tracking the subject.

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": {
      "clipId": "<clipId>"
    },
    "name": "filmcraft_auto_reframe_vertical"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYesTimeline clip ID to reframe
targetSubjectNoSubject to track and keep in center frameprimary speaker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It reveals that subject tracking drives the reframe, which is useful, but says nothing about whether this mutates the original clip in place or produces a new sequence, whether it is destructive, how long processing takes, or whether it can be run repeatedly. For an edit-generating operation with zero annotation coverage this is a substantial gap.

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 well-formed sentence with the target format and mechanism front-loaded and no filler. It is efficient, though it is arguably under-specified rather than optimally concise.

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 tool that transforms a timeline clip, the description omits the outcome entirely: no output schema exists and the description does not say what is returned or where the reframed result lands. With no annotations and no return-value documentation, an agent cannot predict the effect of the call or its result.

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 both clipId and targetSubject are already documented in the schema. The description reinforces the 'subject' concept that targetSubject controls but adds no format, default, or constraint detail beyond what the schema supplies. Baseline 3 applies when the schema does the heavy lifting.

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 states a concrete transformation: 16:9 horizontal to 9:16 vertical, with the mechanism (subject tracking) and the destination use case (Shorts/TikTok). Verb and resource are unambiguous. It loses a point only because it does not distinguish itself from any neighboring tool, though no sibling performs reframing so there is no real confusion risk.

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?

Usage is implied through the target platforms (YouTube Shorts/TikTok), which tells an agent the general context. There is no explicit when-not guidance, no mention of prerequisites such as an open timeline or selected clip, and no alternative named if the agent wanted a manual reframe instead.

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