Skip to main content
Glama

next_video

Skip to the next video in the current playlist to continue watching content without interruption.

Instructions

Skip to the next video in the current playlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'next_video' tool, which triggers a playlist-next command in mpv and returns the updated video status.
    server.tool(
      'next_video',
      'Skip to the next video in the current playlist.',
      {},
      async () => {
        try {
          await mpv.command(['playlist-next']);
          await new Promise((r) => setTimeout(r, 1000));
          const [title, pos, count] = await Promise.all([
            mpv.getProperty('media-title'),
            mpv.getProperty('playlist-pos'),
            mpv.getProperty('playlist-count'),
          ]);
          return textResult({ status: 'skipped_next', title, position: `${Number(pos) + 1}/${count}` });
        } catch (err) {
          return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
        }
      }
Behavior2/5

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

With no annotations provided, the description carries full burden but omits behavioral details: what happens if no playlist is active, if at the end of the playlist, or whether the action is idempotent. Only mentions the playlist context requirement.

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 action verb front-loaded. No redundant words or wasted space. Perfectly sized for the tool's simplicity.

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?

Given zero parameters and no output schema, the description is nearly complete. Minor gap regarding error states or end-of-playlist behavior, but adequate for a simple stateless navigation command.

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?

Input schema has zero parameters. Per evaluation rules, zero-parameter tools receive a baseline score of 4. The description correctly implies no configuration is needed for this navigation action.

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?

The description provides a specific verb ('Skip to'), clear resource ('next video'), and scope ('in the current playlist'). It effectively distinguishes from siblings like prev_video, play_video, and play_similar by specifying the playlist-navigation context.

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?

The phrase 'current playlist' implies a prerequisite state (active playlist session), but lacks explicit guidance on when NOT to use it (e.g., no active playlist) or alternatives for non-playlist contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ronantakizawa/social-video-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server