Autopo

Video frames

video_frames

Draw stills of a video's code film as Studio images (free; seconds after the first build): frames (frame numbers at the film's fps) or every_seconds; neither: the middle of every shot. Up to 12 a call. Needs a passing check. Each result has a url and thumb_url to look at before a render.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video": "<video>"
    },
    "name": "video_frames"
  }
}

Input Schema

Name	Required	Description
`video`	Yes	the video id (list_videos)
`frames`	No
`every_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / frames / items / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost (free), latency (seconds after the first build), a hard per-call cap ('Up to 12 a call'), a precondition ('Needs a passing check'), and the shape of each result (url and thumb_url) with advice to inspect before a render. These are exactly the operational traits the readOnlyHint/destructiveHint flags don't convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and packs mode, limits, precondition, and return shape into a few dense sentences with no filler. It is telegraphic to the point that jargon like 'code film' and 'Studio images' may need context, but nothing is wasted.

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?

With an output schema present, the description needn't detail return values, yet it still flags url/thumb_url and the inspect-before-render workflow. Combined with the precondition and per-call cap, it covers what an agent needs to invoke correctly; only the sibling-routing question is left open.

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 only 33% (only `video` is documented), but the description compensates by defining what `frames` means (frame numbers at the film's fps), what `every_seconds` does, and the default behavior when neither is supplied. It restates the maxItems=12 limit rather than adding new info, keeping it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb+resource ('Draw stills of a video's code film as Studio images') and immediately describes the two selection modes, so an agent knows it extracts frames rather than rendering. It does not explicitly distinguish itself from nearby siblings such as video_keyframes or get_media, which leaves some ambiguity about which still-extraction tool to pick.

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?

Explains the mode selection clearly: pass `frames` for specific frame numbers at the film's fps, `every_seconds` for intervals, or neither for the middle of every shot. It also states prerequisites ('Needs a passing check') and cost/latency ('free; seconds after the first build'). What's missing is guidance on when to use this versus video_keyframes or get_media.

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

All Autopo tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?