Skip to main content
Glama

player_next

Move forward to the next track or video in the playback queue, continuing media playback without interruption.

Instructions

Skip to the next item in the playlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition/schema for player_next - declares the tool name, description, and empty input schema.
    {
      name: "player_next",
      description: "Skip to the next item in the playlist.",
      inputSchema: { type: "object", properties: {} },
    },
  • Handler for player_next - ensures mpv is running, checks if there is a next track in the playlist (fails if at the end), sends playlist-next command to mpv, ensures playback is unpaused, and returns the title of the next track.
    case "player_next": {
      await ensureMpv();
      const plCount = await getProperty("playlist-count").catch(() => 0);
      const plPos = await getProperty("playlist-pos").catch(() => 0);
      if (plCount <= 1 || plPos >= plCount - 1) {
        return fail("已经是最后一首,没有下一曲");
      }
      await mpv("playlist-next", ["weak"]);
      await setProperty("pause", false);
      const nextTitle = await getProperty("media-title").catch(() => null);
      return ok(`Playing next: ${nextTitle || "unknown"}`);
    }
  • index.js:724-729 (registration)
    MCP server registration - tools are listed via ListToolsRequestSchema returning the TOOLS array (which includes player_next), and dispatched via CallToolRequestSchema to handleTool (which handles player_next in the switch case).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
    
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      return handleTool(name, args || {});
    });
Behavior2/5

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

With no annotations, the description is minimal and does not disclose behavior such as return values, failure modes (e.g., at end of playlist), or side effects. The agent lacks critical information about what happens on invocation.

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?

The description is a single, clear sentence with no unnecessary words. It is appropriately sized for a simple, no-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters and no output schema, the description covers the basic purpose but lacks behavioral details (e.g., what if playlist is empty or at end). It is minimally viable but incomplete.

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?

The input schema has zero parameters, so no parameter information is needed. The description does not attempt to explain any nonexistent parameters, and the baseline for 0 params is 4.

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 clearly states the action (skip) and target (next item in playlist), making the purpose unambiguous. However, it does not explicitly differentiate from the sibling player_prev, though the direction is implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like player_play or player_seek. The description lacks context about prerequisites or consequences (e.g., if at end of playlist).

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/guodaxia9527/mcp-mpv-player'

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