Skip to main content
Glama

OpenClip

by app.openclip
OverviewDiscussionsAdmin

Submit Video Tool

submit_video

Submit a source video url (YouTube, Vimeo, Google Drive, Dropbox, OneDrive, Rumble, or a direct video file) to turn into viral clips, with an optional title. Returns the new video id (a hashid) and its status.

Processing is ASYNCHRONOUS: this returns status: "downloading" or a paused pending_credits state. Poll get_video_status with the returned id while processing moves. Do not poll pending_credits: when a failed payment caused the pause, the result includes payment_required: true, a message, and billing_url; show that guidance so the user can repair payment.

Optionally pass an agent id (a hashid from list_agents) to process the video with that agent's settings (caption preset, composition defaults, …); omit it to use the team's defaults.

Optionally pass max_clip_seconds (15 to 90) to cap how long each clip runs (omit it for automatic lengths, 40 to 90 seconds), and clip_guidance (up to 300 characters) to say which moments to prefer, for example "only the funniest reactions". Guidance that is too narrow or not about picking moments is rejected with a reason and a broader suggestion.

Safe to retry: submitting the same url + agent + clip preferences again returns an existing run for it from the last 24h (still processing, or completed) as deduped: true instead of starting a second run. Submitting the same url with a DIFFERENT agent or clip preferences starts a new run (so you can re-process a source with other settings). A previously failed url can be resubmitted to retry it.

Errors: an unsupported/invalid URL is rejected and an agent not on your team is rejected. A missing subscription or insufficient credits parks the video in pending_credits; direct the user to OpenClip before checking again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe source video URL to process (a supported provider or a direct video file).
agentNoOptional agent id (hashid from list_agents) whose settings control processing/rendering. Must be one of your team's agents. Omit to use team defaults.
titleNoOptional title for the video; defaults to the source title.
clip_guidanceNoOptional guidance for which moments to prefer (up to 300 characters). Rejected with a reason and a broader suggestion when too narrow.
max_clip_secondsNoOptional cap on clip length in seconds (15 to 90). Clips then run between half the cap and the cap. Omit for automatic lengths (40 to 90 seconds).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesThe video id (hashid). Pass it as `video` to get_video_status, list_clips, get_render_status and render_clip.
statusYesThe video status. downloading, uploaded and processing are in-flight; pending_credits is paused; completed, failed and download_failed are terminal.
dedupedYesTrue when an existing run for this url + agent + clip preferences from the last 24h was returned instead of starting a new one.
messageNoUser-safe explanation of why processing is paused. Present while the video is pending_credits.
billing_urlNoOpenClip billing page where the user can recover. Present with payment_required or subscription_required.
payment_requiredNoPresent and true when an open failed subscription payment is blocking processing.
subscription_requiredNoPresent and true when terminal payment failure requires a new subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / clip_guidance
      Added value: +{
+  "description": "Optional guidance for which moments to prefer (up to 300 characters). Rejected with a reason and a broader suggestion when too narrow.",
+  "maxLength": 300,
+  "type": "string"
+}
    • addedInput schema / properties / max_clip_seconds
      Added value: +{
+  "description": "Optional cap on clip length in seconds (15 to 90). Clips then run between half the cap and the cap. Omit for automatic lengths (40 to 90 seconds).",
+  "maximum": 90,
+  "minimum": 15,
+  "type": "integer"
+}
    • changedOutput schema / properties / deduped / description
      Previous value: -"True when an existing run for this url + agent from the last 24h was returned instead of starting a new one."New value: +"True when an existing run for this url + agent + clip preferences from the last 24h was returned instead of starting a new one."
  2. Changed1 schema field changed
    • changedOutput schema / properties / message / description
      Previous value: -"User-safe billing recovery guidance. Present with payment_required or subscription_required."New value: +"User-safe explanation of why processing is paused. Present while the video is pending_credits."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "billing_url": {
+      "description": "OpenClip billing page where the user can recover. Present with payment_required or subscription_required.",
+      "type": "string"
+    },
+    "deduped": {
+      "description": "True when an existing run for this url + agent from the last 24h was returned instead of starting a new one.",
+      "type": "boolean"
+    },
+    "message": {
+      "description": "User-safe billing recovery guidance. Present with payment_required or subscription_required.",
+      "type": "string"
+    },
+    "payment_required": {
+      "description": "Present and true when an open failed subscription payment is blocking processing.",
+      "type": "boolean"
+    },
+    "status": {
+      "description": "The video status. downloading, uploaded and processing are in-flight; pending_credits is paused; completed, failed and download_failed are terminal.",
+      "enum": [
+        "downloading",
+        "download_failed",
+        "uploaded",
+        "pending_credits",
+        "processing",
+        "completed",
+        "failed"
+      ],
+      "type": "string"
+    },
+    "subscription_required": {
+      "description": "Present and true when terminal payment failure requires a new subscription.",
+      "type": "boolean"
+    },
+    "video": {
+      "description": "The video id (hashid). Pass it as `video` to get_video_status, list_clips, get_render_status and render_clip.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "video",
+    "status",
+    "deduped"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/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 so richly: asynchronous processing, possible pending_credits pause with payment_required/billing_url, dedup with a 24h window, retry-after-failure, and rejection of invalid URLs or foreign agents. It discloses side effects and failure modes beyond the schema.

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?

Dense but well-structured, with purpose front-loaded and separate paragraphs for async behavior, agent, clip options, dedup, and errors. Every sentence carries actionable content, though the length is near the upper bound for practical scanning.

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 5-param asynchronous submission tool, the description covers inputs, async lifecycle, dedup semantics, error paths, and payment pause guidance. With an output schema present, return-value detail is correctly not duplicated beyond the status hints.

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 already 100%, but the description adds real meaning: the agent hashid comes from list_agents and must be a team agent, clip_guidance rejection behavior and the 'only picking moments' constraint, and how agent/clip preferences interact with dedup. It stops short of full syntax detail but clearly exceeds the schema baseline.

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 (submit), resource (source video url), supported providers, and what it produces (viral clips, returning id + status). It is clearly distinguishable from siblings like render_clip, caption_video, and get_video_status.

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?

Explicitly says when to poll get_video_status vs when NOT to poll (pending_credits), when to pass agent vs omit it, and describes the dedup rule (same url+agent+prefs returns existing run in 24h; different prefs start new run). Alternatives and exclusions are named.

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

All OpenClip 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