Skip to main content
Glama
Sign In
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_add_subtitles

Add a full subtitle track to a JianYing draft by splitting a script into short lines, distributing them evenly across a time window, and returning captions for proofreading.

Instructions

Add a full subtitle track from a script. The script is split into short lines (Chinese ads use ~18 chars/line) and distributed evenly across the time window. Returns the generated lines so they can be proofread.

Input Schema

NameRequiredDescriptionDefault
nameYesOpen draft name
startYesStart time (seconds as a number, or a duration string such as "1m30s")
styleNoText style
trackNoText track index (0 = captions, 1 = titles/overlays) (a number, or a numeric string such as "1")
scriptYesFull narration / caption script
durationYesTotal window (seconds as a number, or a duration string such as "1m30s")
maxCharsNoMax characters per line (default 18)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.20.1
    • changedInput schema / properties / duration / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "durationString": true,
+    "type": "string"
+  }
+]
    • changedInput schema / properties / start / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "durationString": true,
+    "type": "string"
+  }
+]
    • addedInput schema / properties / track
      Added value: +{
+  "acceptsNumericString": true,
+  "description": "Text track index (0 = captions, 1 = titles/overlays) (a number, or a numeric string such as \"1\")",
+  "type": "number"
+}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description does real work by disclosing the line-splitting heuristic (~18 chars/line) and even time distribution, plus that the generated lines are returned. However, it never says whether this replaces existing captions on the track, whether an open draft is required, or whether the operation is reversible – meaningful gaps for a mutation tool with zero annotation coverage.

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?

Three tight sentences with the core action front-loaded and the proofreading return value last. No filler or restatement of the 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?

Adequate for the core script-to-subtitles behavior, and the return value is mentioned. But for a 7-parameter tool with nested style objects and no annotations or output schema, it omits the track targeting semantics (0 vs 1) and overwrite behavior, which an agent needs before calling.

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?

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter semantics the schema cannot express: how script, start, duration, and maxChars interact to produce evenly distributed lines. It still says nothing about how style or track affect the result in prose.

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 ("Add a full subtitle track from a script") plus the mechanics of splitting and distributing. It is clearly distinguishable from jianying_add_text and jianying_export_srt by implication, but no sibling is named explicitly.

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 by the phrase "full subtitle track" and by the note that generated lines are returned for proofreading, which hints at the script-to-captions workflow. There is no explicit guidance on when to prefer this over jianying_add_text or jianying_export_srt, and no stated prerequisites (e.g. draft must be open).

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