Skip to main content
Glama

List a video's clips

list_clips

Retrieve all generated clips for a specific video ID, including each clip's ranking score, timestamps, and title to review or select highlights.

Instructions

The clips from one video: id, score, timestamps and title. Scores are the model's ranking, 0-100.

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": {
      "video_id": "<video_id>"
    },
    "name": "list_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully explains what comes back (id, score, timestamps, title) and defines the 0-100 score semantics, but says nothing about ordering, pagination/limits, error behavior for an unknown video_id, or whether an empty list is possible.

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?

Two short sentences, front-loaded with the resource and then the field/score semantics. Zero filler and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string, no output schema), and the description sensibly covers the return shape in place of a missing output schema. However, with no annotations and no parameter documentation, an agent still lacks guidance on error cases and ordering, so it is adequate rather than complete.

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 0% for the single video_id parameter, so the description must compensate. 'From one video' implies video_id selects a specific video, but it adds no format, source, or lookup guidance (e.g. where to obtain the id, whether it is the same id returned by list_videos).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('clips from one video') and enumerates returned fields, so an agent can tell this apart from list_videos. The verb is implied rather than stated ('The clips from one video' rather than 'List clips'), which slightly weakens the front-loaded purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no alternative mentioned. The phrase 'from one video' hints at a scope contrast with a video-level listing sibling, but the description never says when this tool should be chosen or what preconditions apply (e.g. video must already be queued/known).

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