Skip to main content
Glama

play

Start video playback from a local file or supported streaming URL, with optional controls for seek position, speed, volume, and proxy.

Instructions

Play a video file or URL. URLs from supported streaming sites (YouTube, Bilibili, Twitch, Vimeo, etc.) are extracted via the bundled yt-dlp before playback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "play"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to a local video file, or HTTP(S) URL to a streaming site.
seekNoSeek to position in seconds
proxyNoOptional proxy URL forwarded to yt-dlp for URL extraction (e.g. http://127.0.0.1:7890)
speedNoPlayback speed multiplier
volumeNoVolume level (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add real behavioral value by explaining that streaming URLs are resolved through bundled yt-dlp before playback, but it omits whether the call blocks for the duration of playback, what happens on failure or unsupported URLs, and whether it replaces current playback.

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?

Two sentences, zero filler, front-loaded with the core action and then the one non-obvious behavior (yt-dlp extraction). Every clause earns its place.

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 five-parameter playback tool with no annotations and no output schema, the definition covers the input side adequately but says nothing about return value, blocking semantics, or failure modes. It is minimally sufficient rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each of the five parameters is already documented, and the baseline is 3. The description adds context for the 'file' parameter (URLs get routed to yt-dlp) and implicitly for 'proxy', but adds nothing about seek, speed, or volume beyond the schema.

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 states a specific verb ('Play') and resource ('a video file or URL') and even names the streaming-site case, so an agent can tell it starts playback of a single item. It stops short of naming the sibling it contrasts with (playlist_play), so differentiation is only implied.

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?

Use is implied rather than stated: play a file or a streaming URL. There is no explicit 'use this when / use X instead' guidance against sibling tools like playlist_play, cast, or clip, and no mention of prerequisites such as yt-dlp availability or unsupported sites.

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

Deploy Server

Other Tools