Skip to main content
Glama

List videos

list_videos
Read-onlyIdempotent

List videos across your brands, newest first: generated outputs and files added to a Brand Library. Returns each file's media ID, stable link, source, MIME type, size, duration, and Library status.

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
limitNoNumber of matching items to include on this page. Omit to return 20 items.
cursorNoPass next_cursor from the previous result to get the next page.
sourceNoFilter by how the file was obtained: uploaded for uploaded files, scraped for files collected from brand sources, or generated for model outputs.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
in_libraryNoOnly files in (true) or not in (false) the Library.
brand_session_idNoBrand whose videos to retrieve. Use its Brand session ID from list_brands; omit to leave results unfiltered by brand.

Output Schema

NameRequiredDescriptionDefault
itemsYesMatching files, newest first.
has_moreYesWhether more results follow this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.

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 a safe, idempotent, closed-world read, so the description only needs to add traits beyond that. It does: results are ordered newest first, span all brands by default, and each item carries a stable link plus Library status, which is real behavioral context an agent can rely on.

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 compact clauses, front-loaded with the verb, scope and ordering, and the remainder only lists what comes back. Nothing is padded or repeated.

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?

For a simple filtered list with a full output schema and complete parameter descriptions, this covers purpose, ordering and scope adequately. The only meaningful gap is routing guidance versus the other list_* siblings, and the return-field list partly duplicates the output schema.

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 every parameter — limit default 20, cursor pagination, source enum, in_library, brand_session_id — is already documented. The description's mention of 'generated outputs' and 'Brand Library' loosely maps to source and in_library but adds no syntax or defaults beyond the schema.

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 videos) plus the scope (across brands, newest first) and the two content classes it covers (generated outputs and files added to a Brand Library). It does not name a sibling, so the boundary with list_library / list_generations is left for the agent to infer, which keeps it short of a 5.

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 coverage statement — use it to enumerate generated outputs and Library files — but there is no explicit when-to-use or when-not-to-use guidance against the many sibling list tools (list_images, list_audio, list_library, list_generations).

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