Tegas AI

Edit a finished video

tegas_edit_video

Destructive

Free (no tokens charged). Edit a finished video in place and rebuild it: this REPLACES the whole video end to end and typically takes a few minutes, the same as the original render - it is not a quick patch. Tell the user what you are about to change before calling this, then poll with tegas_wait_video (or tegas_video_status) after the call; do not call this again for the same video until the rebuild finishes.

Pass at least one of the groups below; omit a group entirely to leave it untouched:
- scenes: list of {"index": int, "voiceover_text"?: str, "subtitles_text"?: str, "video_url"?: str}
  - one entry per scene to change, each needs at least one of the three fields.
- voice: {"id"?: str, "gender"?: "female"|"male", "language"?: "ru"|"en"|"es"|"fr"|"de"} -
  changing any of id/gender/language RE-VOICES EVERY SCENE that has voice-over text, not just
  the ones listed in `scenes`.
- subtitles: {"enabled"?: bool, "style"?: "tiktok"|"phrases"|"contrast",
  "appearance"?: {"alignment"?, "font_size"?, "font_family"?, "text_color"? (hex "#RRGGBB"),
  "color_saturation"?}} - you cannot disable subtitles and set their style/appearance in the
  same call, that fails with 422 validation_error; disable them in one call and restyle in a
  later one.
- music: {"enabled"?: bool, "url"?: str} - url must come from tegas_upload_music (or another
  public https URL).
- volumes: {"voice"?: int, "music"?: int, "master"?: int} - each 0..100.
- watermark: bool - the Tegas watermark on the finished video. Must be the ONLY change in the
  call, not combined with scenes/voice/subtitles/music/volumes: the renderer rebuilds the
  watermark through a separate step, so mixing it with other changes fails with 422
  validation_error. Change the watermark in its own call.

Returns video_id, status "processing" and edits_accepted - the list of groups that were actually
applied (e.g. ["voice", "subtitles"], or ["watermark"] for a watermark-only edit). If the video is
still rendering or being rebuilt from a previous edit, this fails with 409 video_busy or edit_in_progress (the edit was NOT accepted) - wait for
status completed (tegas_wait_video) and try again, do not retry immediately in a loop.

Input Schema

Name	Required	Description	Default
`music`	No
`voice`	No
`scenes`	No
`volumes`	No
`video_id`	Yes
`subtitles`	No
`watermark`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and the description substantiates it: the edit replaces the entire video, takes a few minutes, is not a quick patch, and is free. It further discloses failure modes (409 video_busy / edit_in_progress means the edit was NOT accepted; 422 validation_error for watermark-mixing and for disabling plus restyling subtitles in one call) and the response shape. This is far beyond what the annotations alone convey.

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?

Front-loads cost and effect, then uses a scannable bulleted group breakdown with constraints attached to the group they affect. Despite its length, nearly every sentence carries operational information an agent needs (422/409 behavior, watermark isolation, subtitle disable-versus-restyle) that is absent from the schema.

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

Completeness5/5

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

For a 7-parameter destructive mutation with zero schema documentation, this covers purpose, prerequisites, field semantics, cross-field conflicts, busy/retry behavior, and return values. Nothing material is missing, and the presence of an output schema is supplemented rather than merely restated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden — and it does: it enumerates every group with field-level detail, including the critical non-obvious semantic that changing voice id/gender/language re-voices EVERY scene, not just those listed in `scenes`. Enums, ranges (volumes 0..100), hex color format, and 'at least one group, omit to leave untouched' semantics are all supplied.

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?

Opens with a specific verb and resource: 'Edit a finished video in place and rebuild it', and immediately defines the scope of the operation ('REPLACES the whole video end to end'). This clearly separates it from tegas_start_video and tegas_write_scenario, which create rather than modify.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing (poll with tegas_wait_video or tegas_video_status after the call), explicit when-not-to (do not call again for the same video until the rebuild finishes; do not retry in a loop on 409), and prerequisite behavior ('Tell the user what you are about to change before calling this'). It also names the sibling tools that supply dependent inputs, e.g. music url must come from tegas_upload_music.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tegas AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.