Skip to main content
Glama
sonmai

loom-mcp

by sonmai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_frames

Read-only

Extracts up to 10 still frames at specified timestamps from a Loom video URL or ID and returns PNG image paths for review or analysis.

Instructions

Read still frames at 1–10 timestamps, in input order, scaled to 1280 pixels wide.

Accepts an HTTPS Loom share URL or video ID. For every timestamp, returns a text block with seconds and an absolute PNG path, followed by its MCP image content. Files are saved under ~/Library/Caches/loom-mcp/<video_id>/frames/. Downloads and reuses a local MP4 cache. Requires an available MP4 export. Does not modify Loom.

Input Schema

NameRequiredDescriptionDefault
videoYesHTTPS Loom share URL or 32-character hexadecimal video ID.
timestampsYes1–10 positions: seconds (39, 74.5, or '39') or M:SS ('0:39', '1:14'). Each must be finite, non-negative, and less than the video duration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish readOnly, openWorld, and non-destructive behavior, and the description adds substantial context: input-order processing, 1280px scaling, return structure, cache location, local MP4 reuse, and MP4 export prerequisite. It also confirms it does not modify Loom.

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 core action and constraints are front-loaded, then followed by return format and caching details. Every sentence carries operational value for invoking the tool correctly.

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?

With no output schema, the description fully explains the return shape, saved file paths, and MCP image content. It also covers the key prerequisite and cache behavior, leaving no major ambiguity for a two-parameter tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds useful semantics beyond the schema by noting that timestamps are processed in input order and frames are scaled to 1280 pixels wide.

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?

States a specific verb and resource: read still frames at 1–10 timestamps. The action is clearly distinct from sibling tools get_video and get_transcript even without naming them explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the frame-extraction purpose, accepted video input formats, and the requirement for an available MP4 export. However, it does not explicitly say when to choose this over get_video or get_transcript.

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

Deploy Server

Other Tools