Skip to main content
Glama

Ssemble AI Clipping

by com.ssemble
OverviewDiscussionsAdmin

create_short

Create AI-generated short-form video clips from a YouTube video or uploaded file. Returns a request ID instantly. Processing takes 5-30 minutes. Costs 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd time in seconds (> start, max 1200s window)
urlNoYouTube video URL
musicNoAdd background music
startYesStart time in seconds (>= 0)
layoutNoVideo framing layoutauto
ctaTextNoCTA text (max 200 chars, required when ctaEnabled=true)
fileUrlNoPublic video file URL (alternative to url)
languageNoSpoken language (ISO 639-1)en
memeHookNoPrepend a meme hook clip (2-5s attention grabber)
gameVideoNoAdd split-screen gameplay overlay
hookTitleNoAdd animated hook title at start
maxShortsNoMaximum number of shorts to create (1-12). Keeps the highest-scoring clips and never pads, so short videos may return fewer. Omit to get up to 12.
musicNameNoExact track name from list_music (case-sensitive)
ctaEnabledNoShow call-to-action text overlay
noClippingNoSkip AI clipping, process entire range as one clip
templateIdNoCaption template ID from list_templates (24-char hex)
webhookUrlNoOptional webhook URL for completion/failure notifications. Receives a POST with results when processing finishes.
musicVolumeNoMusic volume 0-100
memeHookNameNoExact meme hook name from list_meme_hooks (case-sensitive)
gameVideoNameNoExact game video name from list_game_videos (case-sensitive)
captionLanguageNoCaption language if different from spoken
preferredLengthNoTarget clip durationunder60sec

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / maxShorts
      Added value: +{
+  "description": "Maximum number of shorts to create (1-12). Keeps the highest-scoring clips and never pads, so short videos may return fewer. Omit to get up to 12.",
+  "maximum": 12,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / webhookUrl
      Added value: +{
+  "description": "Optional webhook URL for completion/failure notifications. Receives a POST with results when processing finishes.",
+  "format": "uri",
+  "type": "string"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose three non-obvious traits: asynchronous execution with an immediate request ID, a 5-30 minute processing window, and a cost of 1 credit. It does not state auth requirements, whether the credit is refunded on failure, or that the operation is irreversible (no cancel/undo path is mentioned).

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 short sentences with zero filler, front-loading what the tool does, then the return contract, then latency and cost. Every sentence earns its place and no schema content is restated.

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 22-parameter async creation tool with no output schema, the description covers the return contract (request ID), duration, and cost, which is the essential missing context. The one meaningful gap is the prerequisite tool chain for music/template/meme/game-video selection, though the schema descriptions carry those references.

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 100% across all 22 parameters, so the schema already documents ranges, enums, defaults, and the list_music/list_templates cross-references. The description adds only the url-vs-fileUrl source distinction, which the schema itself already makes. 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 (Create) and resource (AI-generated short-form video clips) plus the two accepted input sources (YouTube URL or uploaded file). This distinguishes it immediately from the list_*/get_*/delete_* siblings, which only read or remove existing requests.

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?

Usage is only implied: 'Returns a request ID instantly. Processing takes 5-30 minutes' hints at an async submit-then-poll flow via get_status, but no alternative or precondition is named. Critically, the description never tells the agent to call list_music, list_templates, list_meme_hooks, or list_game_videos before supplying musicName/templateId/memeHookName/gameVideoName, even though those parameters require exact case-sensitive values from those tools.

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

All Ssemble AI Clipping 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