Skip to main content
Glama

List videos

list_videos
Read-onlyIdempotent

List the caller's videos, newest first, with pagination. Optionally filter by status (one of the VideoStatus values in the schema). Returns id, title, status, videoUrl, thumbnailUrl and timestamps. Requires the "video:read" scope. Read-only, never charges credits.

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
limitNoMax videos to return (default 20, max 100).
offsetNoNumber of videos to skip for pagination (default 0).
statusNoOptional status filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description adds real value beyond them: the required "video:read" scope, the fact that listing never charges credits, deterministic newest-first ordering, and the returned field set. Only the credit/scope notes are genuinely extra behavior, but they are the kind an agent needs before calling.

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?

Four short, front-loaded sentences covering action, filtering, return shape, and permissions, in that priority order. "Read-only" mildly duplicates the readOnlyHint annotation, but the sentence it lives in still contributes the credit-cost clarification.

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?

For a simple read-only list tool with no output schema, the description covers everything needed to call it correctly: scope of data, ordering, pagination, optional filter, required auth scope, and the shape of returned fields.

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 100%, so limit, offset and status are already fully documented including defaults, min/max and the enum. The description only restates that status maps to VideoStatus values and that pagination exists, adding no new syntax or edge-case meaning (e.g. what happens past the last page).

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 the caller's videos") plus ordering ("newest first") and pagination, which cleanly separates it from get_video (single item) and create_video (write). It stops short of naming those siblings explicitly, so differentiation is implied by scope 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 Guidelines3/5

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

Usage is implied: enumerate the caller's own videos, optionally narrowed by status. There is no explicit guidance on when to prefer this over get_video for a known id, or whether results should be paged vs fetched repeatedly.

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.

Resources