Skip to main content
Glama

katto_create_clip_job

Submit a long video by public URL or upload_id to start an asynchronous clipping job that turns it into short vertical clips. Returns a job id to poll or a webhook to notify you on completion.

Instructions

Submit a long video for clipping, either by public link in url (YouTube, Twitch, Kick, Vimeo, Zoom, Google Drive, Dropbox, Loom, LinkedIn, Facebook, Rumble, Dailymotion, Medal.tv, or a direct https link to a video file; Google Drive and Dropbox links must be shared publicly) or, for a local file, by upload_id after katto_upload_video and the PUT of the file. Pass exactly one of url or upload_id. Consumes 1 video from your monthly quota — check katto_get_usage first. Clips are produced asynchronously; returns a job id, then poll katto_get_job every 30-60 s until status is 'completed', or pass webhook_url to be notified (url jobs only). Pass idempotency_key when you might retry a url job, so a retry never spends a second video (an upload can only be started once anyway). Fails if the URL is unsupported, the uploaded file is missing, or the video is longer than your plan allows. Full reference: https://katto.tech/mcp/tools

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "katto_create_clip_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic video URL to clip (YouTube, Twitch, Kick, Vimeo, Zoom, Google Drive, Dropbox, Loom, LinkedIn, Facebook, Rumble, Dailymotion, Medal.tv, or a direct https link to a video file). Pass url OR upload_id.
configNoOptional pre-clip settings.
upload_idNoInstead of url: the upload_id returned by katto_upload_video, once the file has been PUT to its upload_url. Starts clipping that file.
webhook_urlNoOptional https URL that receives a signed POST when the job finishes, so you do not have to poll. Verify the signature with the secret from katto_get_webhook_secret. Private and local addresses are refused.
idempotency_keyNoOptional unique string (max 255 chars). Retrying with the same key returns the original job instead of creating a second one and spending another video. Use one per intended job, e.g. a UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.1
    • addedInput schema / properties / config / properties / clipLength / description
      Added value: +"Target length band for the clips, in seconds. Guides candidate selection by setting a minimum and maximum duration; it is a preference, not a hard cut. Omit to let the model decide."
    • addedInput schema / properties / config / properties / customPrompt / description
      Added value: +"Free-text hint about what matters in this video. Its keywords nudge selection toward matching moments. It does not filter: a clip that matches nothing can still be selected if it scores well."
    • addedInput schema / properties / config / properties / topics / description
      Added value: +"Comma-separated topics to favour. Merged with customPrompt into a single keyword hint, so both bias the ranking rather than restrict it."
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Optional unique string (max 255 chars). Retrying with the same key returns the original job instead of creating a second one and spending another video. Use one per intended job, e.g. a UUID.",
      +  "type": "string"
      +}
    • addedInput schema / properties / upload_id
      Added value: +{
      +  "description": "Instead of url: the upload_id returned by katto_upload_video, once the file has been PUT to its upload_url. Starts clipping that file.",
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"Public video URL to clip."New value: +"Public video URL to clip (YouTube, Twitch, Kick, Vimeo, Zoom, Google Drive, Dropbox, Loom, LinkedIn, Facebook, Rumble, Dailymotion, Medal.tv, or a direct https link to a video file). Pass url OR upload_id."
    • addedInput schema / properties / webhook_url
      Added value: +{
      +  "description": "Optional https URL that receives a signed POST when the job finishes, so you do not have to poll. Verify the signature with the secret from katto_get_webhook_secret. Private and local addresses are refused.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false) it discloses the quota cost (one video from the monthly allowance), asynchrony with polling cadence, webhook availability limited to url jobs, and the three concrete failure modes. The only notable gap is that idempotentHint=false is not reconciled with the idempotency_key behaviour, leaving a small ambiguity about whether same-key retries are truly safe.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the two input modes, then constraints, async behaviour, failure cases, and a reference link, so the order is sensible. It is dense and the long provider enumeration duplicates the url parameter's schema description, which is the only real waste.

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 job-creating tool with no output schema it covers what an agent needs: how to submit, how much it costs, how the result comes back (job id plus polling or webhook), retry safety, and failure conditions. The remaining detail lives in the input schema, which is fully described.

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

Parameters4/5

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

Schema coverage is 100% so the baseline would be 3, but the description adds constraints the schema cannot express: url and upload_id are mutually exclusive, Google Drive/Dropbox links must be publicly shared, and webhook_url only applies to url jobs. It says little about the nested config fields (genre, topics, clipLength, customPrompt), though those are fully documented inline in the schema.

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?

"Submit a long video for clipping" is a specific verb plus resource, and the description immediately enumerates the two intake modes (public url vs. upload_id from katto_upload_video). An agent can tell this is the entry point that creates a clipping job, distinct from katto_get_job (polling) and katto_upload_video (file staging) that are named in the text.

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?

It gives explicit routing rules: pass exactly one of url or upload_id, check katto_get_usage first, then poll katto_get_job every 30-60s or supply webhook_url instead. It also states when to use idempotency_key (retry of a url job) and notes the upload path cannot be restarted, so the agent knows which alternative applies in each scenario.

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