Skip to main content
Glama

List my videos

list_my_videos
Read-only

Lists the signed-in user's most recent ClipFlux videos with their stage, progress and a link to open each one.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many videos, newest first. Default 10.

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=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results are scoped to the signed-in user, ordered newest-first, and include per-item stage, progress and an open link. It omits pagination behaviour (whether there is a cursor beyond limit) but does not mislead.

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 front-loaded sentence with no filler; every clause (who, what, ordering, returned fields) carries information an agent needs to select and call the tool.

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 one-parameter read-only listing with full schema coverage and annotations, this is nearly complete, and the description pre-announces the returned fields in lieu of an output schema. The only gap is the absence of any mention of how large result sets are bounded or whether the 'link' is a shareable URL or an in-app deep link.

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% and the single 'limit' parameter is fully documented in-schema, including default and 1-20 bounds. The description's 'most recent' phrasing corroborates the newest-first ordering but adds no syntax or edge-case detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('Lists the signed-in user's most recent ClipFlux videos') plus the fields returned (stage, progress, link), which clearly separates it from single-video siblings like get_video. It does not explicitly name any sibling, so differentiation is inferred from 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 only implied: 'signed-in user's most recent' tells the agent this is a self-scoped recent-items listing, and 'most recent' hints at the limit ordering. No explicit when-to-use versus get_video or list_scheduled_posts, and no stated exclusions or prerequisites.

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