Skip to main content
Glama

prev_video

Navigate to the previous video in your current playlist while using the social-video-mcp server for YouTube and TikTok playback control.

Instructions

Go back to the previous video in the current playlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the 'prev_video' MCP tool, which executes 'playlist-prev' via the mpv command and returns the new video's status, title, and position.
    server.tool(
      'prev_video',
      'Go back to the previous video in the current playlist.',
      {},
      async () => {
        try {
          await mpv.command(['playlist-prev']);
          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_prev', 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?

No annotations provided, so description carries full burden. While it mentions state dependency on 'current playlist', it fails to disclose what happens when no previous video exists (error, wrap-around, or no-op), whether this modifies browser history, or side effects on playback state.

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?

Perfectly concise at 9 words in a single sentence. Front-loaded with imperative verb 'Go back'. No redundant or filler content; every word serves the definition.

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?

Adequate for a simple stateful navigation tool with no output schema, but incomplete given zero annotations. Missing critical behavioral context such as error conditions (no active playlist, already at first video) and interaction with playback state.

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?

Zero parameters present (empty schema), establishing baseline of 4. The description effectively explains the single implicit 'action' parameter, though no parameter-level semantics are required.

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?

Excellent clarity with specific verb 'Go back', resource 'previous video', and scope 'in the current playlist'. The directional nature clearly distinguishes it from sibling tool next_video, and the playlist context distinguishes it from play_video or seek_video.

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?

Implies usage requires an active playlist via 'current playlist' phrasing, but lacks explicit prerequisites (e.g., 'only works when a playlist is active') or explicit comparison to next_video for navigation direction. No guidance on edge cases like being at the first video.

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