Skip to main content
Glama

List completed clips

list_clips
Read-onlyIdempotent

Retrieves completed live clips from the local clips directory, newest first, returning metadata only for browsing and paging through finished clips.

Instructions

List completed live clips from the local clips directory, newest first, as {"clips": [...]}.

    Each entry has clip_id (a stable ID for the clip; when the server runs with
    --postfling-config, a save_postfling_draft tool also accepts it), channel (Twitch login),
    timestamp (Unix seconds), and, when recorded, duration (seconds), score, and trigger
    (chat, chat_reaction, viewer_clip, elimination, knock, or win). Only clips with a
    valid MP4 and insights sidecar are listed; incomplete or malformed ones are skipped.
    Returns metadata only, never video or chat content. Page with offset until the list
    comes back empty.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100.
offsetNoNumber of newest clips to skip, for paging.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

The annotations declare read-only, non-destructive, idempotent behavior, and the description adds useful context beyond that: newest-first ordering, filtering to clips with valid MP4 and insights sidecar, skipping incomplete or malformed clips, and returning metadata only rather than video or chat content.

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 description is front-loaded with the core action and output shape, then follows with entry fields and filtering details. It is somewhat long, but the additional sentences carry useful operational context rather than filler.

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?

Given the tool is a read-only listing operation with a fully described schema and an output schema, the description covers the remaining important context: valid-clip filtering, metadata-only behavior, output shape, and paging. Nothing critical for correct invocation appears to be missing.

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%, so limit and offset are already documented in the schema. The description adds paging strategy and ordering context, but it does not add much parameter-level meaning beyond what the schema provides.

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?

The description states a specific verb and resource: listing completed live clips from the local clips directory. It also specifies scope, ordering, output shape, and filtering conditions, so an agent can understand exactly what the tool does without opening the 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?

It gives explicit paging guidance: page with offset until the list comes back empty. It does not name alternatives or exclusions, but no sibling tools are provided and the context is clear enough for correct use.

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