Skip to main content
Glama

get_frames

Read-onlyIdempotent

Fetch keyframe images from a screen recording at a specific timestamp or across a time range, up to 6 frames per call.

Instructions

Fetch stored keyframe images (JPEG, <=1568px wide) as MCP image content: the frames nearest to at_ms, OR unique frames across [start_ms, end_ms] evenly thinned to max_frames. Serves unique frames by default (near-duplicates from static scenes are filtered); hard cap 6 images per call. When NOT to use: exact instants between keyframes or native-resolution detail (use extract_frame), or finding on-screen text (use search — OCR text is indexed). Examples:

  • get_frames(job_id="...", at_ms=83500) — what was on screen when the remark at 1:23.5 was spoken

  • get_frames(job_id="...", at_ms=83500, max_frames=2) — tighter context, fewer tokens

  • get_frames(job_id="...", start_ms=0, end_ms=600000, max_frames=6) — overview strip of the first 10 min

  • get_frames(job_id="...", start_ms=290000, end_ms=310000, include_duplicates=true) — every capture near 5:00

  • transcript hit at t_ms=421500 → get_frames(job_id, at_ms=421500) for the visual evidence

  • walking a demo scene by scene → one ranged call per scene beats one giant range

  • frame files are named by video-ms (t00083500.jpg ↔ t_ms 83500) — stable refs for findings

  • valid_from_ms/valid_to_ms on each frame = when the screen looked like this — check the span covers your moment

  • keep max_frames at 2-4 unless you are truly comparing scenes; images are token-expensive

  • every frame entry carries "path" (absolute) — save/copy the image elsewhere with your own file tools

  • audio-only job → this tool errors by design; use get_transcript / get_moment instead

  • anti-example: need EXACTLY 12:34.500 between two keyframes → extract_frame(job_id, at_ms=754500)

  • anti-example: "find the screen with the red error banner" → search(job_id, "error") first, then jump

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
at_msNo
end_msNo
job_idYes
start_msNo
max_framesNo
include_duplicatesNo
Behavior5/5

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

Annotations already declare read-only/idempotent safe, but the description adds substantial behavioral detail: hard cap of 6 images, deduplication of near-duplicates, error on audio-only jobs, file naming convention, valid_from_ms/valid_to_ms semantics, and path field disclosure. No contradiction with annotations.

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?

Long but efficiently structured: core behavior, when-not, examples, anti-examples, and field tips. Every bullet adds actionable info; front-loaded with the primary fetch behavior, and the length is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description compensates by explaining return content (MCP images, path, valid_from/valid_to), error cases, and practical usage limits. Complete for an agent to select and invoke correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, so description must and does explain semantics. It clarifies at_ms (nearest), start/end_ms (range), max_frames (thinning), include_duplicates (every capture), and job_id via examples, fully compensating for the schema gap.

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 opens with a specific verb ('Fetch') and resource ('stored keyframe images') plus format constraints (JPEG, <=1568px). It clearly differentiates from siblings by naming extract_frame for exact instants/native resolution and search for text, and get_transcript/get_moment for audio-only jobs.

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

Usage Guidelines5/5

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

Explicitly lists 'When NOT to use' with alternatives (extract_frame, search) and provides anti-examples. Examples show when to use, including ranged vs at_ms, include_duplicates, and transcript-driven lookups, giving clear decision guidance.

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/korovin-aa97/talkthrough-mcp'

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