Skip to main content
Glama

get_status

Check current video playback status including title, position, duration, and pause state for YouTube or TikTok videos playing in the mpv player.

Instructions

Get the current playback status: title, position, duration, and pause state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_status' tool is registered and implemented directly in src/index.ts. It fetches media-title, time-pos, duration, and pause state from mpv and returns them formatted.
    server.tool(
      'get_status',
      'Get the current playback status: title, position, duration, and pause state.',
      {},
      async () => {
        try {
          const [title, position, duration, paused] = await Promise.all([
            mpv.getProperty('media-title'),
            mpv.getProperty('time-pos'),
            mpv.getProperty('duration'),
            mpv.getProperty('pause'),
          ]);
          return textResult({
            title,
            position: typeof position === 'number' ? `${Math.floor(position)}s` : null,
            duration: typeof duration === 'number' ? `${Math.floor(duration)}s` : null,
            paused,
          });
        } 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?

With no annotations provided, the description must carry the full burden. It compensates for the missing output schema by listing the returned data structure, but omits behavioral details such as what happens when nothing is playing, cache freshness, or if this requires an active session.

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 that front-loads the action ('Get') and immediately specifies the return payload. No redundant words or structural waste.

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?

For a simple state-retrieval tool with no input parameters, the description is adequate. It compensates for the lack of output schema by documenting the return fields, though it could note the scope (current player vs specific video).

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 tool has zero parameters and the schema is empty. Per the evaluation rules, zero-parameter tools receive a baseline score of 4.

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 the tool retrieves 'playback status' and specifically enumerates the returned fields (title, position, duration, pause state). This effectively distinguishes it from action-oriented siblings like play_video, pause_video, and 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?

While the description implies this is a query tool versus the command siblings (play, pause, seek), it lacks explicit guidance on when to call this versus get_video_info or whether it should be polled or called on demand.

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