Skip to main content
Glama

List videos

list_videos
Read-onlyIdempotent

Your newest 50 videos (AI swaps and your own), newest first, in pages: limit (default 20) and cursor (next_cursor from the previous page). active_only: only those still being made.

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
limitNoItems per page (default 20, up to 100)
cursorNonext_cursor from the previous page; omit for the first page
active_onlyNo

Output Schema

NameRequiredDescriptionDefault
videosYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real behavior: a hard cap of 50 items, newest-first ordering, and how paging works via cursor chaining — none of which appear in the annotations.

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?

One sentence, front-loaded with scope and ordering, then pagination, then the optional filter. No filler or repeated annotation text; every clause carries information.

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

Completeness4/5

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

An output schema exists, so return-value explanation is unnecessary, and the three parameters are all accounted for. The only rough edge is the mismatch between a stated 50-item ceiling and a limit that allows up to 100 — an agent may reasonably wonder whether that ceiling is real.

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 67%, with limit and cursor already documented in the schema. The description adds value mainly for active_only, which has no schema description, by defining it as 'only those still being made', and reinforces the default-20 and next_cursor chaining semantics.

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?

States a specific verb and resource (list your videos) plus the scope: your newest 50, including both AI swaps and your own, newest first. That scope wording separates it from get_video and list_characters without naming them, though no sibling is explicitly contrasted.

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

Usage Guidelines3/5

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

Usage is implied by the 'your newest 50 videos' framing and the pagination note, which tells the agent this is the browse/enumerate path. It never states when to prefer a different tool (e.g. get_video for a single item) or any prerequisite, so guidance stops at implication.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.