Skip to main content
Glama

Tegas

by ai.tegas
OverviewDiscussionsAdmin

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 - wait for
status completed (tegas_wait_video) and try again, do not retry immediately in a loop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
musicNo
voiceNo
scenesNo
volumesNo
video_idYes
subtitlesNo
watermarkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces and expands on this: it explicitly states the call REPLACES the whole video end to end, takes several minutes, and is not a quick patch. It also discloses failure modes (422 validation_error for illegal combinations, 409 video_busy) and notes that the operation is free. This goes well beyond what annotations alone provide.

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 long but every section earns its place: the most critical warning (full rebuild, not a quick patch) is front-loaded, parameter groups are organized into scannable bullets, and constraints are placed next to the parameters they affect. There is no redundant restatement of the schema or filler content.

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 tool with an empty schema-coverage rating and complex interaction rules, the description covers everything needed: return values (video_id, status, edits_accepted), error handling (409, 422), polling guidance, and the destructive cost of the operation. An agent can confidently decide when and how to invoke the tool without additional external knowledge.

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?

With 0% schema description coverage and open object types, the description carries the full burden of parameter documentation. It details each parameter group with field lists, types, omission behavior, and constraints—e.g., scenes entries need at least one of three fields, volumes range 0..100, and watermark must be a standalone change. This is exemplary compensation for an uninformative 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?

The description states a specific action ('Edit a finished video in place and rebuild it') and clearly scopes the resource: a finished video. It differentiates itself from creation and status tools through the 'finished video'/rebuild framing, but it doesn't explicitly name an alternative like tegas_start_video. This is clear enough to avoid confusion, though not maximally explicit on sibling differentiation.

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 explicit operational guidance: tell the user before calling, poll with tegas_wait_video or tegas_video_status, and do not call again for the same video until the rebuild finishes. It also provides precise conditional rules, such as watermark must be the only change and subtitles cannot be disabled and restyled in the same call. It doesn't contrast itself with alternatives for editing vs. creating, but within its own domain the usage guidance is thorough.

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

All Tegas toolsInspect
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.

Resources