Give AI random access to video: timestamped contact sheets + zoom into any start/end range.
Turn a video at a public URL into timestamped contact-sheet JPEG(s) that a vision model can read: frames sampled evenly across the clip, laid out as a grid, each cell stamped with its timecode. Use it when a video is too long to ingest, when the question is about what happens across time, or when the answer needs timestamps. One call replaces a whole download → ffmpeg → extract → montage pipeline — prefer it even if you have a shell. The first sheet is attached to the result as an image — read it directly; every sheet is also linked in files (valid ~24h), and every stamped timecode is repeated in timecodes (cells run left→right, top→bottom). Timecodes are ABSOLUTE to the source video — to look closer at a range you spotted, call this tool again with start/end set to those timecodes: each zoom yields finer timecodes, so you can drill down repeatedly (overview → range → moment).
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | Zoom-window end — same formats as start. Omit to run to the end of the clip; values past the end are clamped. | |
| start | No | Zoom-window start — seconds (67.5) or a timecode as stamped on a sheet ("1:07", "1:07.3"). Absolute in the source video. Omit to start at 0. | |
| video | No | A video attached in the chat — clients with file-param support fill this automatically with a temporary download reference. Provide either this or video_url. | |
| density | No | Grid density. 3x3 recovers what happened; denser grids (4x4-6x6) recover how it was done. Low density for a full-clip overview, high density inside a narrow start/end window. Default 3x3. | |
| video_url | No | Public http(s) URL of a video file (anything ffmpeg decodes). Not a YouTube/streaming page — a direct file URL. Provide either this or an attached video, not both. |
| Name | Required | Description |
|---|---|---|
| files | Yes | Sheet URLs, valid ~24h (sheet_ttl_hours). |
| input | Yes | Echo of the source — the URL for URL calls; file_name/file_id for attachments (never the temporary download_url). |
| frames | Yes | Frames sampled across the clip or window. |
| job_id | Yes | |
| layout | Yes | Where each cell sits on each sheet, in sheet pixels — same order as files, index-aligned with timecodes (cells[n] is the frame stamped timecodes[n]). Published because it cannot be derived: gutters, an outer margin and the branding band mean the grid does not fill the image, so dividing width/height by columns and rows is wrong. Crop by these rectangles to show a single frame. IMPORTANT: these describe the full-resolution sheets at files[], NOT the inline image block — that preview is re-encoded down a size ladder to fit the result budget, so it is often smaller. To crop the inline preview instead, scale every rectangle by (its decoded width / layout[0].width). |
| sheets | Yes | Number of contact sheets produced. |
| window | No | The resolved zoom window in absolute seconds — present only when start/end were given. |
| contract | Yes | Always "squish-mcp-http-v0". |
| duration | Yes | Source video duration, seconds. |
| warnings | Yes | |
| timecodes | Yes | Per-sheet stamped timecodes, cells left→right then top→bottom — mirrors every label burned into the sheets. Absolute to the source video at every zoom depth. |
| credits_charged | No | Keyed calls only. |
| sheet_ttl_hours | Yes | |
| credits_remaining | No | Keyed calls only. |
| free_jobs_remaining_today | No | Anonymous calls only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false, so they don't mention duration links, expiry, timecode lists, or attachment behavior. The description discloses all of these: attached image read directly, files valid ~24h, `timecodes` repeated, cells ordered, absolute timecodes, clamping, and the ability to zoom/drill down by re-invoking start/end. That's exactly the kind of behavioral context an agent cannot infer from metadata this description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is efficient and front-loaded: the core purpose appears in the first sentence, then use cases and the manual-pipeline comparison, then output details, then recurring invocation pattern. Every sentence continues by a new idea without repeating the same message, and the structure moved from user's intent to output to zooming guidance—exactly what an agent needs in one pass.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description does not need to invent a return-value spec, but it uses exactly the available pieces: it explains how to consume the returned images, how long links last, how to read the `timecodes` array, and how to call back with start/end for higher resolution. The only source of ambiguity is solved by declaring the URL type (direct `http(s)` file, not a streaming page) and the public-URL requirement. For a five-parameter tool with nested objects, this is complete enough to call independently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already has informative parameter notes (density suggestions, start/end formats, clamp, attachment alternative), so the baseline is 3; this description goes at least one step further by clarifying how `start`/`end` are used to 'drill down' with refined timecodes and by reinforcing the `video` vs `video_url` either/or rule ('not bringing both'). It doesn't add new info for every parameter, but stands above 'neutral'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the verb ('turn... into') and two resources (a video → 'timestamped contact-sheet JPEG(s)') with details on frame sampling, grid layout, and timecode stamping. It also specifies the target reader ('vision model') and what output format to expect, making the tool’s purpose unmistakable even without reading the schema. There are no sibling tools, so no differentiation is needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It says exactly when to use this tool: 'when a video is too long to ingest', 'when the question is about what happens across time', or 'when the answer needs timestamps'. It also names the concrete alternative (download → ffmpeg → extract → montage pipeline) and explicitly says to 'prefer it even if you have a shell', leaving no doubt about the intended tradeoff.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
squish_video2 fields changedOutput schema / properties / layoutAdded value: +{
+ "description": "Where each cell sits on each sheet, in sheet pixels — same order as files, index-aligned with timecodes (cells[n] is the frame stamped timecodes[n]). Published because it cannot be derived: gutters, an outer margin and the branding band mean the grid does not fill the image, so dividing width/height by columns and rows is wrong. Crop by these rectangles to show a single frame. IMPORTANT: these describe the full-resolution sheets at files[], NOT the inline image block — that preview is re-encoded down a size ladder to fit the result budget, so it is often smaller. To crop the inline preview instead, scale every rectangle by (its decoded width / layout[0].width).",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "cells": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "blank": {
+ "description": "True when that frame could not be read and the cell was left black. Present on EVERY cell — a missing field means a server older than this contract, not a healthy sheet. Blankness is NOT detectable from the image: every cell is painted black before drawing, so a night shot or a cut to black is pixel-identical to a failed read.",
+ "type": "boolean"
+ },
+ "h": {
+ "type": "number"
+ },
+ "w": {
+ "type": "number"
+ },
+ "x": {
+ "type": "number"
+ },
+ "y": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "x",
+ "y",
+ "w",
+ "h",
+ "blank"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "height": {
+ "type": "number"
+ },
+ "width": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "width",
+ "height",
+ "cells"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Output schema / requiredPrevious value: -[
- "input",
- "duration",
- "frames",
- "sheets",
- "files",
- "sheet_ttl_hours",
- "warnings",
- "timecodes",
- "job_id",
- "contract"
-]New value: +[
+ "input",
+ "duration",
+ "frames",
+ "sheets",
+ "files",
+ "sheet_ttl_hours",
+ "warnings",
+ "timecodes",
+ "layout",
+ "job_id",
+ "contract"
+]squish_videoClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Video analysis AI: transcripts, summaries, visual scenes/shots, clips, answers in natural language.
Understand your videos with Reka AI — search, ask questions, and extract insights.
A real timeline video editor for AI agents: journaled edits, FFmpeg/MLT rendering, exports
Edit video by talking to your AI — search footage, cut timelines, apply effects, add captions.
Add one secure layer between your agents and this server.
Only one tool exists, so there is no possibility for an agent to confuse it with another. The tool's purpose is clearly and comprehensively described.
The single tool name 'squish_video' follows a clear verb_noun pattern. With only one tool, there are no conflicting conventions or broken patterns.
A single-tool server feels thin even if the tool is useful and well-defined. The count is borderline but acceptable for the extremely narrow 'video to contact sheet' purpose.
Within its narrow domain, the tool covers the full workflow: overview generation, timestamps, and iterative zooming. Minor gaps such as supporting non-public URLs or local file uploads are not significant for the stated use case.
