Skip to main content
Glama
Ppppan9

jianying-editor

by Ppppan9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jianying_open_draft

Open an existing JianYing draft by name and return its timeline structure to inspect or resume editing; set overwrite only to discard the draft and start over.

Instructions

Open an existing JianYing draft by name and return its timeline structure, so work can be resumed. Use this to inspect or continue a draft listed by jianying_list_drafts. Pass overwrite only to deliberately discard the existing draft and start over.

Input Schema

NameRequiredDescriptionDefault
nameYesDraft name (the folder name inside the drafts root)
overwriteNoDiscard the existing draft and start an empty one. This deletes it — omit it to resume editing.
draftsRootNoOverride the drafts root directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.20.1
    • changedInput schema / description
      Previous value: -"Open a JianYing draft"New value: +"Open an existing JianYing draft"
    • removedInput schema / properties / fps
      Removed value: -{
-  "description": "Frame rate (default 30)",
-  "type": "number"
-}
    • removedInput schema / properties / height
      Removed value: -{
-  "description": "Canvas height (default 1080)",
-  "type": "number"
-}
    • changedInput schema / properties / overwrite / description
      Previous value: -"Replace the draft if it already exists"New value: +"Discard the existing draft and start an empty one. This deletes it — omit it to resume editing."
    • removedInput schema / properties / width
      Removed value: -{
-  "description": "Canvas width (default 1920)",
-  "type": "number"
-}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the highest-risk behavior: overwrite deliberately discards the existing draft. It also states the return value (timeline structure). It omits the session/lifecycle implication of the open/close pair (does the draft stay locked until jianying_close_draft?) and error behavior for a missing name.

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 short sentences, no filler, and the core action is front-loaded before the routing hint and the destructive-flag caveat. Every sentence earns its place.

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?

Absent an output schema, the description usefully names what comes back (timeline structure), and it covers the one dangerous option. What's missing is the open/close session relationship implied by jianying_close_draft, which an agent needs to use this tool correctly in a workflow.

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 all three parameters carry their own explanations, so the schema does the heavy lifting. The description reinforces overwrite's risk but adds no syntax or format detail for name or draftsRoot beyond what is already structured. Baseline 3 applies.

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?

States a specific verb and resource ("Open an existing JianYing draft by name") plus the effect ("return its timeline structure") and the intent ("so work can be resumed"). An agent can distinguish this from jianying_create_draft and jianying_list_drafts without opening the schema.

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?

Explicitly routes from a listing step ("a draft listed by jianying_list_drafts") and gives a clear conditional rule for the overwrite flag versus resuming. However, it says the tool is used "to inspect" a draft, which overlaps with the sibling jianying_inspect_draft and never resolves when to pick one over the other.

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