SnapDub

Make clips from a video

create_video

Turns a long video link (YouTube, Twitch, Kick, Rumble or Zoom) into short vertical clips with captions. Spends credits; processing takes a few minutes to tens of minutes depending on length. Returns the new video's video_id and status; the clips are listed once its status is "done".

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_video"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Link to the source video.
`clips`	No	How many clips to make. Defaults to 6.
`captions`	No	Burn captions into the clips. Defaults to true.
`template`	No	Name of one of the account's templates (see list_templates) to apply its style.
`translate_to`	No	Language code to translate the captions into, e.g. "es". Leave out to keep the original language.
`clip_length_seconds`	No	Longest a clip may run, in seconds. Defaults to 180.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations cover the safety profile, while the description adds meaningful operational context: it spends credits, runs asynchronously for minutes to tens of minutes, and returns a video_id and status. It does not explain authentication, idempotency implications, or how to retrieve the final clips beyond waiting for status "done".

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 compact sentences, front-loaded with what the tool does, followed by cost/latency and return behavior. There is no filler and each sentence carries distinct operational information.

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?

With no output schema, the description usefully explains that creation returns a video_id and status and that clips become available once status is "done". It is largely complete for an asynchronous creation tool, though it could explicitly point to list_clips or get_video for follow-up.

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 100%, so all six parameters are already documented in the schema. The description adds platform support and mentions captions, but gives no additional guidance on clips count, template selection, translation, or clip length beyond what the schema provides.

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?

The description states a specific verb and resource: turns a source video link into short vertical clips with captions. It names supported platforms and makes clear this creates a new video/clip job rather than retrieving or listing existing videos.

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

Usage Guidelines3/5

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

It implies the tool is for long source videos and warns about credit spend and processing time, but it does not explicitly say when to use this versus alternatives like get_video or list_clips. No exclusions or alternative workflows are named.

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

All SnapDub 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.

Resources

Need Help?