Schema | movingimagearchive

movingimagearchive

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Tools

Functions exposed to the LLM to take actions

Name	Description
search_clipsA	Search the archive for individual shots by a visual description (semantic/CLIP search, e.g. 'red sunset over water', 'crowd at a 1930s world fair'). Leave `query` empty to browse all shots in archive order. Returns shot timing, source film and direct MP4 links for the shot and the full film. Pass `nextOffset` back as `offset` for more.
list_sourcesB	List the source films in the archive (the site's Gallery), with archive totals. Each film has a slug for get_source and a full-film download link.
get_sourceA	Get one source film: title, year, running time, synopsis, provenance & rights (original producer, collection, original Internet Archive link), full-film download URL and its shot list with per-shot download URLs.
list_collectionsA	List the archive's curated, themed collections of shots (e.g. Cats, Film Countdowns, Space Flight) with their slugs and shot counts.
get_collectionB	Get the shots in one curated collection, with timing, source film and download links.
downloadA	Save footage to a local MP4 (never overwrites an existing file). Pass exactly one of `clipId` (a single shot) or `sourceSlug` (the full film). To get only part of it, add `startSeconds` and/or `endSeconds` (relative to that shot or film), or, with `sourceSlug`, `fromShot`/`toShot` (1-based, inclusive, like shift-click on the site). Ranges need ffmpeg on PATH; only that part is fetched and it is re-encoded for frame-accurate cuts. If you only need a link, use the URLs returned by the other tools instead.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored 2026-10-24 19:30 across 6 tools

Disambiguation5/5

Each tool has a clearly distinct role: search shots, list source films, get one source film, list curated collections, get one collection, and download footage. The download tool explicitly disambiguates itself from URL-returning tools. No two tools overlap in a confusing way.

Naming Consistency4/5

Most names follow a clear verb_noun snake_case pattern: search_clips, list_sources, get_source, list_collections, get_collection. The lone exception is download, which lacks a noun but is still unambiguous. This is mostly consistent with a minor deviation.

Tool Count5/5

Six tools is well-scoped for a moving image archive: search, browse films, inspect a film, browse collections, inspect a collection, and download. Each tool earns its place without redundancy or obvious missing surface area.

Completeness4/5

The surface covers searching clips, browsing and inspecting source films and collections, and downloading clips or full films. Minor gaps exist, such as no dedicated get_clip-by-id tool and no direct collection-level download, but these are workable via search results and existing download options.

Maintenance

ActivityMaintained

ResponsivenessNo issues