Skip to main content
Glama

list_my_videos

List the signed-in Epic Video user's finished videos, newest first, with playback URLs.

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
limitNoMaximum number of videos to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does add real behavioral detail: read-only listing, newest-first ordering, only completed videos, and that playback URLs are included in the response. It says nothing about pagination beyond the limit parameter, behavior when the limit is reached, or auth requirements beyond the 'signed-in' cue, which leaves meaningful gaps for an unannotated tool.

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 the resource and scope, and every clause (finished, newest first, playback URLs) carries information an agent needs. Nothing is redundant or padded.

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 single-parameter read tool with no output schema, the description covers the essentials — whose videos, which state, ordering, and what the return includes. The only shortfall is the absence of any pagination or result-cap behavior, which is a modest gap given the limit parameter.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains limit, its default of 20, and the 1–100 range. The description adds no constraints or semantics beyond that, which is the expected baseline when the schema does the work.

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 names a specific verb ('List') and a precisely scoped resource ('the signed-in Epic Video user's finished videos'), plus ordering and payload ('newest first, with playback URLs'). It distinguishes itself from create_video and get_job_status by implication (existing, finished items rather than creation or job tracking), though it never names a sibling explicitly.

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' signals this is self-scoped rather than a lookup of arbitrary users, and 'finished' signals it excludes in-progress jobs (which get_job_status would cover). There is no explicit statement of when to prefer this over list_characters or create_video, and no exclusions stated.

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.