Skip to main content
Glama

thumbnail

Extracts a still JPG from a video at a specified timestamp—defaulting to the middle—to create a post cover image.

Instructions

A still picture (JPG) from the video at at seconds (default: the middle), for a post's cover.

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": {
      "video": "<video>"
    },
    "name": "thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
videoYes

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?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds the output format (JPG) and the default timestamp behavior, but does not say where the image is stored, whether an existing asset is overwritten, or what happens if the timestamp is out of range.

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?

A single compact sentence that front-loads the output type and then the selector. Nothing is wasted, though the extreme brevity is what leaves the gaps noted above.

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, no-output-schema tool this covers the essentials: what is produced, the format, and the timing default. The missing piece is the `video` reference format, which matters for correct invocation.

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 0%, so the description carries the burden. It meaningfully documents `at` (seconds, defaults to the middle of the video) but leaves `video` unexplained — no indication whether it is a path, ID, or URL, despite being the required parameter.

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 concrete result (a JPG still from the video) and the selecting parameter, so an agent can tell this is a frame-extraction tool rather than a crop, export, or clip-extension tool. It stops short of naming a contrasting sibling, but the verb+resource is specific enough to disambiguate.

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 phrase 'for a post's cover' implies the intended use case, which is more than nothing. However, it gives no explicit when-to-use versus when-not guidance and does not point to any alternative for related tasks such as exporting or cropping frames.

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