Skip to main content
Glama
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_create_draft

Create a new JianYing draft with a set name, canvas size, and frame rate. When width and height are omitted, the canvas adopts the first video's resolution.

Instructions

Create a new JianYing draft and return its structure. Set width/height to match the source footage (1080x1920 for 9:16 vertical, 1920x1080 for 16:9). When omitted, the canvas adopts the first video's resolution automatically.

Input Schema

NameRequiredDescriptionDefault
fpsNoFrame rate (default 30) (a number, or a numeric string such as "1")
nameYesDraft name
widthNoCanvas width (a number, or a numeric string such as "1")
heightNoCanvas height (a number, or a numeric string such as "1")
overwriteNoReplace an existing draft with the same name. Off by default, because overwriting discards the existing project.
draftsRootNoOverride the drafts root directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.20.1
    • addedInput schema / properties / fps / acceptsNumericString
      Added value: +true
    • changedInput schema / properties / fps / description
      Previous value: -"Frame rate (default 30)"New value: +"Frame rate (default 30) (a number, or a numeric string such as \"1\")"
    • addedInput schema / properties / height / acceptsNumericString
      Added value: +true
    • changedInput schema / properties / height / description
      Previous value: -"Canvas height"New value: +"Canvas height (a number, or a numeric string such as \"1\")"
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Replace an existing draft with the same name. Off by default, because overwriting discards the existing project.",
+  "type": "boolean"
+}
    • addedInput schema / properties / width / acceptsNumericString
      Added value: +true
    • changedInput schema / properties / width / description
      Previous value: -"Canvas width"New value: +"Canvas width (a number, or a numeric string such as \"1\")"
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the non-obvious default that omitting width/height makes the canvas adopt the first video's resolution, and mentions returning the draft structure. It says nothing about where the draft is written, whether a subsequent jianying_save_draft is required for persistence, or what permission/filesystem preconditions exist.

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?

Three short sentences, front-loaded with what the tool does, followed by the one genuinely non-obvious parameter rule. No filler, though the aspect-ratio advice reads slightly like a tip rather than definitional content.

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?

No output schema exists, and "return its structure" is vague about what a draft structure actually contains. For a disk-writing mutation with no annotations, the missing lifecycle context (persistence/save requirement, drafts root default, run-twice behavior on duplicate names) leaves real gaps.

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; the description earns above that by explaining the coupled semantics of width/height and their fallback behavior, which the schema does not convey. fps, overwrite, and draftsRoot are left entirely to the schema.

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?

"Create a new JianYing draft and return its structure" names a specific verb and resource, and the create-vs-open distinction against jianying_open_draft is implicit in the verb. It stops short of explicitly differentiating itself from the other lifecycle siblings (open/save/list), so not a 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?

It gives concrete guidance for choosing width/height (1080x1920 for 9:16, 1920x1080 for 16:9) and states the omission behavior, which is genuine usage help. But there is no guidance on when to call this versus jianying_open_draft or jianying_list_drafts, and no prerequisites stated.

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