Skip to main content
Glama

video_frame

Read-only

Capture the current frame of a video playing in a shared tab as an image, falling back to a cropped screenshot when the site blocks video access.

Instructions

Get the current frame of a video on a shared tab as an image. Falls back to a cropped screenshot when the site doesn't allow reading the video.

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": {
      "ref": "<ref>"
    },
    "name": "video_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe video's ref from list_media or snapshot.
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds genuinely new behavioral context: the tool degrades to a cropped screenshot when the site blocks video reading, so the agent knows it may receive a fallback image. It does not state the image format or dimensions, but the core degradation behavior is disclosed.

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 short sentences with no filler, and the primary behavior is front-loaded ahead of the fallback caveat.

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 two-parameter read-only tool with no output schema and fully documented parameters, the definition covers what the agent needs: what is returned (an image) and what happens when site restrictions apply. Only the image format/size is left unstated, which is minor.

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 coverage is 100%, so both parameters (ref, tab) are already documented in the schema, including the tab-optional-when-single condition. The description adds nothing about what ref values look like or how the tab handle interacts with the call, so baseline 3 applies.

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 names a specific verb and resource ("Get the current frame of a video ... as an image") and scopes it to a shared tab. It also implicitly separates itself from the generic screenshot sibling by describing the cropped-screenshot fallback, though it never names that sibling explicitly.

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 implied by the precondition that a video exists on a shared tab, and the fallback clause hints at the relationship with plain screenshots. There is no explicit when-to-use/when-not guidance or a named alternative for the non-video case.

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