Skip to main content
Glama

Outil.io

Get video export frame

get_video_export_frame
Read-only

Inspecter visuellement une image du MP4 terminé : composition, transitions, textes et effets réellement rendus.

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": {
      "exportId": "<exportId>"
    },
    "name": "get_video_export_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
exportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the useful behavioral point that results reflect what was actually rendered rather than the project source, but says nothing about return format (an image), cost/latency of rendering a frame, or failure modes for a missing or in-progress export.

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?

A single front-loaded sentence with no filler; the purpose and the inspected aspects come immediately. It is terse to the point of omitting parameters, but there is no redundant wording to trim.

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

Completeness2/5

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

The tool is simple (2 params, no output schema), yet the definition never states that a frame image is returned, never explains the time parameter, and gives no precondition about export completion. For a tool whose only two inputs are undocumented elsewhere, this is under-specified.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it carries none. Neither 'exportId' (required UUID) nor 'time' (0-600, default 0) is mentioned; an agent gets no clue whether time is seconds or milliseconds, nor whether omitting it yields the first frame.

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?

Names a specific verb+resource: visually inspecting an image of the finished MP4, enumerating what is checked (composition, transitions, texts, effects). The phrase 'MP4 terminé' implicitly separates it from the source-frame sibling, though it does not name that sibling directly.

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 only implied: inspecting the *finished* export suggests post-render verification, which points away from get_video_source_frame and get_video_export. There is no explicit when-to-use statement, no prerequisite (must the export be complete?), and no named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.