Skip to main content
Glama

Vyexa — video link to short clips

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).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "create_clips"
  }
}

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.
dub_languageNoAI voice-over in this language (original voice removed, background kept); limited per plan.
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. Changed1 schema field changed
    • changedInput schema / properties / dub_language / enum
      Previous value: -[
      -  "en",
      -  "ru",
      -  "uk",
      -  "pl",
      -  "es",
      -  "de",
      -  "fr",
      -  "tr",
      -  "ar",
      -  "ja",
      -  "ko",
      -  "id"
      -]New value: +[
      +  "en",
      +  "es",
      +  "de",
      +  "uk",
      +  "ru",
      +  "pl",
      +  "fr",
      +  "tr",
      +  "ar",
      +  "ja",
      +  "ko",
      +  "id"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / dub_language
      Added value: +{
      +  "description": "AI voice-over in this language (original voice removed, background kept); limited per plan.",
      +  "enum": [
      +    "en",
      +    "ru",
      +    "uk",
      +    "pl",
      +    "es",
      +    "de",
      +    "fr",
      +    "tr",
      +    "ar",
      +    "ja",
      +    "ko",
      +    "id"
      +  ],
      +  "type": "string"
      +}
  3. 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
      +]
  4. 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."
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover only the safety profile (not read-only, open world, not idempotent), and the description adds the substantive behavior: it returns a job_id immediately, runs asynchronously for a few minutes, can complete as "partial", and num_clips is a maximum rather than a guarantee. It also discloses the billing consequence — it consumes the account's normal clip balance, free plan included — which annotations cannot express.

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?

Four dense sentences, front-loaded with what the tool produces, then the async contract, then the caveat about output count and cost. Every sentence carries information an agent needs before calling.

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?

For a complex 15-parameter async mutation with no output schema, the description covers the job lifecycle, the polling sibling, and the partial-completion state. It leaves minor gaps — no guidance on validation failures, unsupported/private URLs, or what the job record contains beyond job_id — but the essential call-and-poll loop is complete.

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 93%, so the schema already documents nearly every parameter including enum values and plan gating. The description only adds the nuance that num_clips is a maximum not a guarantee; with 15 parameters it cannot meaningfully elaborate the rest, so the baseline 3 is appropriate.

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 — cuts a video link into vertical 9:16 short clips with burned-in subtitles — and enumerates the supported source platforms. An agent can distinguish this from list_clips (browsing) and get_job (polling) without opening any 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 says this starts a job and that the caller must poll get_job until status is "completed" or "partial", naming the correct sibling for the follow-up step. It does not state when not to use it or contrast with list_clips/get_options, so it falls short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources