Back to MCP tools

pre-alpha · v0.1.0

get_frames

SEE the video: extract labeled still frames at the given timestamps (seconds) from a studied video's stored media.

Inputs

Types and defaults come from source annotations. Constraints described below still apply; the schema is not runtime SDK output.

slugRequired
text
timestampsRequired
list of number
Full input schema
{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string"
    },
    "timestamps": {
      "type": "array",
      "items": {
        "type": "number"
      }
    }
  },
  "required": [
    "slug",
    "timestamps"
  ]
}

Outputs and behavior

SEE the video: extract labeled still frames at the given timestamps (seconds) from a studied video's stored media. Up to 8 per call (6 recommended). Sample at shot boundaries (shots[].start), hook window 0-3s first, and judge frames together with the transcript; frames alone under-perform. Frames are 1024px longest-edge JPEGs extracted on demand; nothing is cached.

The tool description documents its results and behavior. An exact output schema is not supplied; fields not described here are unknown.

What touches the network

This tool's description does not specify its network behavior. Tool-specific details are unknown.

Zing's network policy

Studying, rendering and memes run locally by default. Reference URL downloads require explicit consent. Requested model and font downloads are pinned by URL and SHA-256, cached locally and reported. Uoink is reached only through a peer you configure on your machine. Zing has no telemetry or analytics.

Source

Generated from the site's synced MCP inventory on every build. Descriptions and input schemas refer to this pinned source snapshot.

Source commit: d308dc3f9c2b42e305afd4d7d61e4bfa2f276bc4

Read the tool manifest