Skip to main content
Glama
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_add_text

Adds a text or subtitle segment to a JianYing draft's text track, letting you create titles, lower thirds, and single captions with configurable timing, style, and track placement.

Instructions

Add a text or subtitle segment to the text track. Use for titles, lower thirds and single captions.

Input Schema

NameRequiredDescriptionDefault
nameYesOpen draft name
textYesText content
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")
durationYesDuration (seconds as a number, or a duration string such as "1m30s")
subtitleNoUse the caption defaults — smaller size, an outline, and the low caption position

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / subtitle
      Added value: +{
+  "description": "Use the caption defaults — smaller size, an outline, and the low caption position",
+  "type": "boolean"
+}
    • 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

B3.3/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 does not say whether the draft must be open first, whether the change is persisted or requires jianying_save_draft, whether it returns a segment identifier, or what happens when segments overlap on the same track. For a mutation tool 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.

Conciseness5/5

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

Two sentences, zero waste, with the core action front-loaded and the use cases following immediately. Nothing is padded or repeated.

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?

A 7-parameter mutation tool with a nested style object and no output schema deserves more than this: the draft-lifecycle context (open/save) and the return value are unaddressed. The rich schema covers the input surface well, which keeps it at minimum viable rather than inadequate.

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%, including nested style fields, the enum for align, and the meaning of the track index (0 = captions, 1 = titles/overlays). The description adds almost no parameter-level meaning, so the baseline 3 applies.

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?

Specific verb and resource ('Add a text or subtitle segment to the text track') plus concrete use cases (titles, lower thirds, single captions). The word 'single' implicitly separates it from the sibling jianying_add_subtitles, but the sibling is never named so the distinction must be inferred.

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?

'Use for titles, lower thirds and single captions' gives an implied usage context and hints that bulk captioning belongs elsewhere. It never names jianying_add_subtitles as the alternative, and it does not state the prerequisite that a draft must already be open (the sibling jianying_open_draft exists).

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