Skip to main content
Glama

SizeMyFile

Extract video frames

video_frames
Idempotent

Sample a video at a chosen interval and download PNG frames in a ZIP for review or reference. Up to 32 MiB input/output and ten minutes of media. FFmpeg WebAssembly runs in a worker; small settings and clips work best on mobile. Automatic mode may use native FFmpeg in Kubernetes when the browser runs out of resources. At most 100 frames. Sampling interval and maximum output dimensions keep output bounded. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "video_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

The description goes well beyond the annotations: it discloses hard limits (32 MiB, ten minutes, 100 frames maximum), says the work runs in a WebAssembly worker, notes a Kubernetes fallback, and critically says the call queues a run and returns an ID instead of the result. It also flags that cloud allowance is consumed. The missing piece is what happens on failure or when the queue is full.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key capability comes first, followed by limits, execution model, and the async contract, which is a sensible order. A few sentences, such as the Kubernetes fallback detail, are implementation trivia that take up space without changing an agent's decision.

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?

The output schema covers the return value, and the description sensibly adds the queued-run contract and the size limits. However, for a tool with four parameters at 0% schema coverage and a nested options object, leaving three parameters unexplained means the definition is not complete enough for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, and it only alludes to the interval ("chosen interval"); it never explains artifacts, idempotency_key, or allow_server_fallback. It also mentions "maximum output dimensions" even though no such parameter exists in the schema, which actively misleads.

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?

A concrete verb and resource are stated ("Sample a video at a chosen interval and download PNG frames in a ZIP"), which clearly separates it from a plain video_compress or video_gif. It never names a sibling or explicitly rules one out, so the differentiation is implicit rather than explicit.

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?

Usage is only implied through environment constraints: the mobile note and the browser-versus-Kubernetes fallback, plus the general framing "for review or reference." There is no guidance on when to choose this over a sibling such as video_gif, and no conditions under which it should not be used.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.