Skip to main content
Glama
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_add_video

Add a video or image clip to a JianYing video track; omit the start time to append it after existing content for quick timeline assembly.

Instructions

Add a video or image clip to a video track. When 'start' is omitted the clip is appended after the current track content.

Input Schema

NameRequiredDescriptionDefault
nameYesOpen draft name
speedNoPlayback speed multiplier
startNoTimeline start (seconds as a number, or a duration string such as "1m30s")
trackNoVideo track index (0 = bottom layer, 1 = overlay) (a number, or a numeric string such as "1")
volumeNoClip volume 0..1
durationNoClip length; defaults to the rest of the file (seconds as a number, or a duration string such as "1m30s")
filePathYesAbsolute path to the media file
sourceStartNoOffset inside the source file (seconds as a number, or a duration string such as "1m30s")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / sourceStart / 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 / acceptsNumericString
      Added value: +true
    • changedInput schema / properties / track / description
      Previous value: -"Video track index (0 = bottom layer, 1 = overlay)"New value: +"Video track index (0 = bottom layer, 1 = overlay) (a number, or a numeric string such as \"1\")"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully explains that omitting 'start' appends the clip after current track content, but it does not cover permissions, draft prerequisites, overwrite behavior, or error conditions for this mutation tool.

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?

The description is two focused sentences with no wasted text. The core action is front-loaded, followed by the most important behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with eight fully documented parameters and no output schema, the description is largely complete: it states the action and the key default for 'start'. It could better mention draft prerequisites or mutation side effects, but the rich schema covers most calling details.

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 the schema already documents all parameters thoroughly. The description adds the useful default behavior for omitted 'start', but it does not add meaning beyond the schema for the other parameters.

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?

The description states a specific verb and resource: add a video or image clip to a video track. It clearly distinguishes this from sibling tools like jianying_add_audio and jianying_add_text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use it by specifying video tracks and visual media. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of full routing guidance.

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