Skip to main content
Glama

Last frame of a video

last_frame

Extracts the final frame of a finished video as a new start image for a follow-up shot, returning an upload image reference to pass into generate.images.

Instructions

Extracts the last frame of a finished video as a new start image, for a follow-up shot that continues seamlessly. Returns an image reference ("upload:…") to pass in generate.images.

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": {
      "id": "<id>"
    },
    "name": "last_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGallery id of a finished video

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose the key non-obvious facts: the source must be a *finished* video, and the return value is an image reference string prefixed 'upload:…'. It omits failure behavior for unfinished or invalid videos and any cost/latency expectations, which keeps it below a 5.

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. The purpose comes first and the return-value shape follows, which is the order an agent needs it in.

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 one-parameter, annotation-free tool with no output schema, the description covers purpose, selection context, and return format — the pieces an agent cannot get elsewhere. Only error/edge-case behavior is left unstated.

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?

There is a single parameter with 100% schema description coverage, where the schema already says 'Gallery id of a finished video'. The description reinforces the finished-video constraint but adds no format or lookup guidance beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb (extracts) and a specific resource/artifact (the last frame of a finished video, returned as a start image), plus the downstream use case. No sibling tool in the list does this, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the condition that motivates the call — creating a follow-up shot that continues seamlessly — and tells the agent where the result goes (generate.images). It never states when not to use it, but for a narrowly scoped one-parameter tool the intended context is clear enough.

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