Skip to main content
Glama

List processed videos

list_videos

Retrieve processed videos with their clip counts, ordered newest first, to review generated captioned clips and select which to publish.

Instructions

Videos Clips Kitty has processed, newest first, with clip counts.

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_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does deliver two useful behavioral facts: results are sorted newest first and each entry carries a clip count. It omits volume limits, pagination behavior, whether all history is returned, and any auth or scope caveats, which matters for a list endpoint that could return a large set.

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?

A single compact clause with zero filler, and the most useful information (recency ordering and clip counts) is packed in front. It is a sentence fragment rather than a structured statement, which slightly weakens front-loading of the tool's primary action.

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?

For a zero-parameter list tool with no output schema, the description should at least cover return shape and scope, and it covers ordering and per-item clip counts but not pagination, result limits, or whether the vast majority of processed videos are included. Adequate but with clear gaps given how simple the schema is.

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?

The tool takes zero parameters, which normally sets a baseline of 4, but there is nothing parameter-related for the description to clarify and it adds no filtering or scoping semantics. Three is appropriate for a no-arg tool whose description does not mention how the empty input constrains results.

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 ('Videos Clips Kitty has processed') and adds distinguishing attributes: ordering ('newest first') and payload ('with clip counts'). It doesn't use a verb or explicitly contrast with the sibling list_clips, so differentiation is only implied by the word 'videos' rather than stated.

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, no mention of when to prefer this over list_clips, and no stated prerequisites or exclusions. The agent must infer the routing decision from the resource noun alone.

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