Skip to main content
Glama
clipugc

clipugc

Official
by clipugc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get clip or finished video status

get_video
Read-only

Check the status of a clip or finished video. Poll create_clip, create_motion_clip, or merge_ad results to see pending, processing, completed, or failed status.

Instructions

Get the current status of a clip (kind "clip", default; same as clipugc videos status <id>) or of a finished video (kind "finished"; same as clipugc finished show <videoId>). This is the poll tool for create_clip, create_motion_clip and merge_ad. Status is pending, processing, completed or failed. A clip record also carries merge_status and merged_video_id once a finished video was made from it. Costs no credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesClip or finished video id, as returned by other tools (numbers are fine as strings).
kindNo"clip" (default) for a clip id, "finished" for a finished video id (merged_video_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.0
    • changedInput schema / properties / id / description
      Previous value: -"Clip or ad id, as returned by other tools (numbers are fine as strings)."New value: +"Clip or finished video id, as returned by other tools (numbers are fine as strings)."
    • changedInput schema / properties / kind / description
      Previous value: -"\"clip\" (default) for a character video id, \"ad\" for a merged_video_id."New value: +"\"clip\" (default) for a clip id, \"finished\" for a finished video id (merged_video_id)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "clip",
-  "ad"
-]New value: +[
+  "clip",
+  "finished",
+  "ad"
+]
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare that this is a read-only operation, so the description carries real weight by disclosing the status state machine (pending/processing/completed/failed), the presence of merge_status and merged_video_id on clip records, and that the call costs no credits. It stops short of timing/backoff guidance for polling, which keeps it off a 5.

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?

The primary purpose and mode split are front-loaded in the first sentence, followed by the polling role and return states. It is information-dense but every sentence contributes; the inline CLI command references add length without adding much for an agent.

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?

With no output schema, the description supplies the return semantics that matter — the status enum, the merge fields, and the zero-cost guarantee — plus the polling relationship to three creator tools. An agent has everything needed to call it correctly and interpret the result.

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 is 3, but the description adds meaning on top: it states that kind defaults to "clip" and that "finished" expects the merged_video_id from a clip record. The enum value "ad" is left unexplained in both schema and description, which is the only gap.

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, and splits the resource into two distinct modes (clip vs finished video) with their CLI equivalents. It explicitly identifies itself as the poll tool for create_clip, create_motion_clip and merge_ad, so an agent can place it precisely among siblings.

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?

The description clearly says when to reach for it: polling the status of ids returned by create_clip, create_motion_clip and merge_ad. It gives no explicit "do not use for X" exclusion (e.g., how it differs from download_video or list_* tools), but the usage context is unambiguous.

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

Deploy Server

Other Tools