Skip to main content
Glama

pause_video

Pause or resume the currently playing video in the social-video-mcp server to control playback during AI-assisted video interactions.

Instructions

Toggle pause/resume on the currently playing video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'pause_video' tool, which uses the mpv library to cycle the pause state of the video.
    server.tool(
      'pause_video',
      'Toggle pause/resume on the currently playing video.',
      {},
      async () => {
        try {
          await mpv.command(['cycle', 'pause']);
          const paused = await mpv.getProperty('pause');
          return textResult(paused ? 'Video paused.' : 'Video resumed.');
        } catch (err) {
          return errorResult(`Error: ${err instanceof Error ? err.message : String(err)}`);
        }
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It successfully explains the toggle behavior (pausing if playing, resuming if paused), but omits error handling (what happens if no video is active), return values, and side effects.

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 consists of a single 7-word sentence that is front-loaded with the action ('Toggle pause/resume'). Every word earns its place; there is no repetition of the tool name or redundant schema information.

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?

Given the tool's simplicity (state toggle with no inputs/outputs) and lack of annotations, the description covers the essential function. However, it lacks completeness regarding error conditions (no active video), return values, and explicit differentiation from the stop_video sibling.

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 contains zero parameters. Per the evaluation rules, zero-parameter tools receive a baseline score of 4. The description appropriately does not invent parameter semantics where none exist.

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 uses specific verbs ('Toggle pause/resume') and identifies the target resource ('currently playing video'). It implicitly distinguishes from siblings like stop_video (terminate playback), play_video (start new content), and seek_video (change position) by emphasizing 'currently playing' and the toggle mechanism.

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 description provides implied usage context through the word 'toggle' (indicating it switches between states) and 'currently playing' (indicating it requires active media). However, it lacks explicit guidance on when to use this versus stop_video or prerequisites like requiring an active video session.

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