Skip to main content
Glama

List uploaded videos

clipember_list_media
Read-onlyIdempotent

The user's own uploaded videos (the Media library), newest first by default. filter: all | unused (not in any post) | in_use | expiring (deleted automatically within 7 days); sort: newest | expiring (soonest automatic deletion first); q searches the file name. Each video has its mediaId, status, duration, how many posts use it and expiresAt (when it is deleted automatically; null while a post still needs it). Pass nextCursor back as cursor, with the same sort, for the next page.

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": "clipember_list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch in the file name
sortNoDefault newest
limitNo1–100, default 20
cursorNonextCursor from the previous page
filterNoDefault all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and non-destructive; the description adds substantive behavior on top: the returned fields (mediaId, status, duration, post usage count, expiresAt), the non-obvious null semantics of expiresAt while a post still needs the asset, and the requirement to resend the same sort alongside nextCursor.

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?

Front-loaded with the resource and default ordering, then dense semicolon-separated clauses that each carry information. The density makes it slightly hard to scan, but there is no filler or redundancy.

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?

No output schema exists, yet the description enumerates the meaningful return fields and pagination contract, and covers every enum parameter's meaning. For a five-parameter optional-filter list tool, an agent has everything needed to call it and interpret results.

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 100%, so the baseline is 3, but the description adds real meaning beyond it by defining the filter and sort enum values in operational terms and tying cursor to the same sort. It does not mention limit bounds or default, which the schema already documents.

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?

States a specific verb and resource with scope: "The user's own uploaded videos (the Media library)", plus the default ordering. It is clearly distinguishable from sibling listers such as clipember_list_broll_assets or clipember_list_clips by naming the owned-upload Media library.

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?

Explains what each filter and sort value selects (unused = not in any post, expiring = auto-deleted within 7 days), which effectively tells an agent when each mode applies, and gives explicit pagination instructions for cursor reuse. It stops short of naming an alternative such as clipember_get_media for fetching a single video by id, so no explicit when-not guidance.

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