Skip to main content
Glama

Vyexa — video link to short clips

by net.vyexa
OverviewDiscussionsAdmin

Create short clips from a video link

create_clips

Start a job that cuts a video link (YouTube, TikTok, Instagram, Vimeo, Twitch, or a direct file URL) into vertical 9:16 short clips with burned-in subtitles. Returns a job_id immediately; the job runs for a few minutes — poll get_job until status is "completed" or "partial". num_clips is a maximum, not a guarantee. Uses the account's normal clip balance (free plan included).

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https link to the source video.
fontNoFont: montserrat, rubik, russo.
logoNoPaid plans only: {url|base64, position, size, margin, opacity}. See https://vyexa.net/api-docs#logo.
titleNoFixed title instead of an AI one. Max 32 characters (70 when constructor.title_style is "newsline"); longer is cut.
layoutNoFraming: auto, full, frame_70, frame_50, frame_40, dual, streaming, lesson. See get_options.
languageNoSpoken language code (en, ru, uk, pl, …) or "auto" (default).
num_clipsNoMaximum number of clips to produce (default 1).
title_styleNoTitle style: clean, box, chip, box_accent, newsline, outline, off.
generate_titleNoGenerate an AI title for each clip (default true).
subtitle_styleNoSubtitle style, e.g. karaoke, highlighter, glow, punch, none. See get_options.
highlight_colorNoAccent colour as #RRGGBB (or "#RRGGBB+#RRGGBB" for two alternating).
profanity_censorNoMask and bleep swear words.
segment_durationNoClip length category. 0 (default) = Auto: length picked per clip from content, mixed short/medium/long, every plan. 30 Short and 65 Medium need Creator, 120 Long needs Pro. Legacy 50/90 = 65/120.
subtitle_positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / segment_duration / description
      Previous value: -"Target clip length in seconds. 50 needs Creator, 90 needs Pro; default 30."New value: +"Clip length category. 0 (default) = Auto: length picked per clip from content, mixed short/medium/long, every plan. 30 Short and 65 Medium need Creator, 120 Long needs Pro. Legacy 50/90 = 65/120."
    • changedInput schema / properties / segment_duration / enum
      Previous value: -[
-  30,
-  50,
-  90
-]New value: +[
+  0,
+  30,
+  65,
+  120
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / title / description
      Previous value: -"Fixed title instead of an AI one."New value: +"Fixed title instead of an AI one. Max 32 characters (70 when constructor.title_style is \"newsline\"); longer is cut."
    • changedInput schema / properties / title / maxLength
      Previous value: -32New value: +70
    • changedInput schema / properties / title_style / description
      Previous value: -"Title style: clean, box, chip, box_accent, outline, off."New value: +"Title style: clean, box, chip, box_accent, newsline, outline, off."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=false, openWorld=true, destructive=false), the description discloses that this is an asynchronous job returning a job_id immediately, that it takes minutes, and that it consumes the account's clip balance including free plans. No contradiction with annotations; failure/retry behavior is the main omission.

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-loaded with the action and output format in the first sentence, then job semantics, then the num_clips caveat, then billing. Four sentences, each contributing distinct information with no repetition.

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?

Covers the essential lifecycle an agent needs for a 14-parameter async mutation: the returned job_id, expected duration, polling target, and cost model, against a high-coverage schema and no output schema. Minor gaps remain around error handling and what 'partial' means for results.

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 coverage is 93%, so the schema carries nearly all parameter meaning including plan gating and enums. The description only adds the nuance that num_clips is a cap rather than a guarantee, which is already partly implied by the schema's 'Maximum number of clips to produce'.

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?

Specific verb and resource: 'start a job that cuts a video link … into vertical 9:16 short clips with burned-in subtitles', with the supported sources enumerated. It is clearly distinguishable from siblings get_job, get_options, and list_clips.

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 the agent to get_job for polling and names the terminal statuses 'completed' or 'partial', and warns that num_clips is a maximum. It doesn't state when to prefer list_clips or when a job would be rejected, but the sequencing guidance is clear.

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

All Vyexa — video link to short clips 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