Skip to main content
Glama

AIClipMaker.org

Process a video into short clips

process_video

Start clipping a video from its URL. AIClipMaker.org downloads the source itself, transcribes it, finds the most viral moments with AI and renders vertical (9:16) clips. Captions are burned by default. Takes the URL as the user gave it; the video does not need to be opened or transcribed beforehand. Returns a job_id immediately — the work takes minutes; poll get_job_status or pass webhook_url to be called back. The caller must own the content or hold the rights to process it (confirm_rights).

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": {
      "confirm_rights": "<confirm_rights>"
    },
    "name": "process_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_urlNoPublic video URL, passed through exactly as the user gave it (YouTube watch/short/live URL, TikTok video URL, or a direct video file URL). The server does the downloading.
webhook_urlNoOptional public HTTPS URL POSTed once when the job finishes or fails.
target_clipsNoHow many clips to aim for. A target, not a guarantee: fewer come back when the material doesn't hold them. Default: the AI decides (usually 2-6).
confirm_rightsYesMust be true: the user owns the content or has rights to process it.
webhook_secretNoOptional secret; the webhook body is then HMAC-SHA256 signed (X-AIClipMaker-Signature, also sent as X-OpenShorts-Signature).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source_url / description
      Previous value: -"Public video URL, passed through exactly as the user gave it (YouTube watch/short/live URL or a direct video file URL). The server does the downloading."New value: +"Public video URL, passed through exactly as the user gave it (YouTube watch/short/live URL, TikTok video URL, or a direct video file URL). The server does the downloading."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds the genuinely load-bearing behavior: this is an async job that returns a job_id immediately, runs for minutes, and requires a rights assertion via confirm_rights. It also discloses the server-side side effects (downloading the source, burned-in captions by default) that the 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?

Front-loaded with the action, then cost/timing expectations, then follow-up mechanism, then the legal prerequisite. Every sentence carries information an agent needs before calling; no filler or restated headings.

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?

No output schema exists, so the description must cover the return value, and it does: job_id returned immediately with minutes of latency, plus the polling and webhook callback paths. Rights requirements, defaults (burned captions, AI-chosen clip count) and async semantics are all present for a five-parameter open-world mutation.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description reinforces source_url ('takes the URL as the user gave it') and webhook_url (callback instead of polling), but adds little beyond what the schema already says about target_clips, webhook_secret or confirm_rights.

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 ('Start clipping a video from its URL') and then spells out the full pipeline: download, transcribe, find viral moments, render vertical 9:16 clips. An agent can distinguish this from get_job_status and list_clips 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?

Gives clear context for use and explicitly routes follow-up: 'poll get_job_status or pass webhook_url to be called back', plus 'the video does not need to be opened or transcribed beforehand', which preempts a wrong prerequisite step. It stops short of stating when NOT to use it (e.g. an already-running job), so it is not fully exhaustive.

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