VideoGenerationMCP

Overview Schema Source Related Servers Discussions Admin

extract_frame

Save a video frame as a PNG at a specified time (or the last frame by default), with optional upload to a temporary public URL for use as a reference in multi-clip video generation.

Instructions

Save one frame of a video (local path or URL) as PNG; default = LAST frame.

Use the last frame of clip N as image_first of clip N+1 (generate_seedance_first_last) to bridge multi-clip continuity. With upload=true the frame is also hosted on a temporary public URL so it can be passed as a reference directly.

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": "extract_frame"
  }
}

Input Schema

Name	Required	Description	Default
`video`	Yes
`time_s`	No
`upload`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description discloses some behavior: default is the last frame, upload=true hosts a temporary public URL, and output is PNG. However, it doesn't mention side effects like asset creation or how to access the saved frame, leaving some behavioral aspects unclear.

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?

The description is two sentences, front-loaded with the core purpose, followed by a practical use case and upload behavior. No redundant wording; every sentence earns its place.

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 three-parameter tool with no annotations, the description covers the core function, default behavior, upload option, and a common workflow. It omits specifics about time_s and output details, but an output schema exists, so return values may be documented there.

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 0%, so the description must compensate. It clarifies 'video' (local path or URL) and 'upload' (hosts on temporary public URL). 'time_s' is only implied by 'default = LAST frame,' without stating that it selects a specific frame or its units, leaving ambiguity.

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 the tool's function clearly: 'Save one frame of a video (local path or URL) as PNG; default = LAST frame.' It uses a specific verb and resource, and the mention of bridging continuity with generate_seedance_first_last distinguishes it from siblings.

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 concrete usage guidance: 'Use the last frame of clip N as image_first of clip N+1...' and explains when upload=true is useful. It doesn't explicitly state when not to use it or name alternatives, but the reference to a sibling tool indicates integration context.

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