Skip to main content
Glama
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_add_audio

Add BGM, voiceover, or sound effects to a JianYing draft by placing an audio file on track 0 or 1 with optional start time, volume, and fades.

Instructions

Add an audio clip (BGM, voiceover, sound effect) to an audio track. Use track 0 for the main audio bed and track 1 for narration.

Input Schema

NameRequiredDescriptionDefault
nameYesOpen draft name
startNoTimeline start (seconds as a number, or a duration string such as "1m30s")
trackNoAudio track index (0 = BGM, 1 = narration) (a number, or a numeric string such as "1")
fadeInNoFade-in length (seconds as a number, or a duration string such as "1m30s")
volumeNoVolume 0..1
fadeOutNoFade-out length (seconds as a number, or a duration string such as "1m30s")
durationNoClip length (seconds as a number, or a duration string such as "1m30s")
filePathYesAbsolute path to the audio 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. Changed7 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 / fadeIn / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "durationString": true,
+    "type": "string"
+  }
+]
    • changedInput schema / properties / fadeOut / 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: -"Audio track index (0 = BGM, 1 = narration)"New value: +"Audio track index (0 = BGM, 1 = narration) (a number, or a numeric string such as \"1\")"
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it is thin for a mutation tool. It does not say whether the draft must be open first, whether the change is reversible, whether saving is required afterwards, how duration behaves when omitted, or what the response looks like. The only behavioral content is track routing, which already appears in the schema.

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?

Two front-loaded sentences with the core action and track routing first. The second sentence largely restates the schema's track description, a small redundancy, but overall it is tight with no padding.

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?

This is a 9-parameter mutating tool with no annotations and no output schema, and the description leaves key agent questions unanswered: draft-open prerequisite, save requirement, duration defaults, and failure modes. The rich schema compensates on parameter semantics but not on behavior or workflow position.

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% and every parameter, including duration-string formats and volume ranges, is documented in the schema. The description adds no parameter meaning beyond what is already there, so the baseline of 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?

The description opens with a specific verb and resource ('Add an audio clip') and enumerates the usable audio types (BGM, voiceover, sound effect), which clearly separates it from jianying_add_video, jianying_add_text, and jianying_add_subtitles. It does not name a sibling or state exclusions, so it stops short of 5.

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 track 0 for the main audio bed and track 1 for narration' gives real routing guidance for one parameter, which is implied usage rather than when-to-use-vs-alternatives guidance. Nothing tells the agent when this tool is the right choice over another add_* sibling, nor what prerequisites apply.

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