list_videos
List the account's videos, newest first. Filter by status and limit the count to keep responses small.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Default 20. | |
| status | No |
vivideo
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses ordering behavior ('newest first') and filtering/limit functionality, but lacks details on response format or pagination, though adequate for a list tool without annotations.
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?
Single, efficient sentence with key action front-loaded; no wasted words.
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?
Complete for a simple list tool with two parameters and no output schema; covers ordering, filtering, and limit rationale.
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?
Adds value beyond the input schema by explaining that limit controls response size and status filters results, partially compensating for 50% schema description coverage.
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?
Description clearly states 'List the account's videos, newest first' with specific verb and resource, distinguishing from sibling tools like get_video or create_manual_video.
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?
Provides guidance on filtering by status and limiting count to keep responses small, but does not explicitly exclude scenarios or mention alternatives.
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.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool has a clear, distinct purpose. There is no overlap between tools like check_account and check_configuration, or between the two create video modes. All list tools target different entities, and the remaining tools serve unique roles (estimate credits, get video, wait for video, render preview).
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case, such as check_account, create_auto_video, list_models. This makes it easy to predict tool names and understand their purpose.
Tool Count5/5
With 13 tools, the number is well-scoped for a video generation API. It covers setup, account management, creation (two modes), credit estimation, retrieval, listing of various resources, and video waiting. No tool feels redundant or missing.
Completeness4/5
The tool surface covers the core workflow well: configuration check, account info, video creation (both auto and manual), credit estimation, retrieval, and listing. However, there are no tools for updating or deleting videos, nor for managing resources beyond listing (e.g., creating avatars or brand kits). These are minor gaps.