Skip to main content
Glama

get_frame_burst

Read-onlyIdempotent

Extract evenly-spaced frames from a video time range to analyze motion, vibration, shaking, flickering, or animations where scene-change detection fails. Specify start and end timestamps and number of frames (max 30).

Instructions

Extract multiple frames evenly distributed across a time range.

Designed for motion and vibration analysis where scene-change detection fails because the "scene" doesn't change — only the position/state of objects does.

Example: get_frame_burst(url, "0:15", "0:17", 10) → 10 frames in 2 seconds

  • AI sees the object in different positions across frames → understands the vibration

  • Works for: shaking, flickering, animations, fast scrolling, loading spinners

Supports: Loom (loom.com/share/...) and direct video URLs (.mp4, .webm, .mov). Requires video download capability — direct URLs work best.

Args:

  • url: Video URL

  • from: Start timestamp (e.g., "0:15")

  • to: End timestamp (e.g., "0:17")

  • count: Number of frames (default: 5, max: 30)

Returns: N images evenly distributed between the from and to timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesVideo URL (Loom share link or direct mp4/webm URL)
fromYesStart timestamp (e.g., "0:15")
toYesEnd timestamp (e.g., "0:17")
countNoNumber of frames to extract (default: 5)
returnBase64NoReturn frames as base64 inline instead of file paths
Behavior4/5

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

Description adds behavioral context: requires video download capability, supports specific URL types, returns N images. Annotations already indicate readOnlyHint=true and idempotentHint=true; description enhances with operational details.

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?

Well-structured: brief purpose, use case, example, supported URLs, parameter list, return description. Every sentence adds value, no fluff.

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?

Covers purpose, use case, parameters, example, supported types, and return. Minor omission: does not describe returnBase64 parameter despite being in schema. Overall comprehensive for a tool with no output schema.

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 baseline is 3. Description adds default and max for count, and explains from/to purpose. However, it omits mention of returnBase64 parameter. Adequate but not exceptional.

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?

Description clearly states 'Extract multiple frames evenly distributed across a time range' and specifies use case for motion/vibration analysis. Differentiates from siblings like get_frame_at (single frame) by focusing on burst extraction.

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?

Provides explicit when-to-use context (motion/vibration analysis where scene-change detection fails) and an example. Does not explicitly exclude alternatives but context implies differentiation. Consider giving explicit contrast with get_frames sibling.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guimatheus92/mcp-video-analyzer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server