Skip to main content
Glama

export_current_frame

Export the current timeline frame as a full-resolution still image to a specified file path, supporting formats such as DPX, TIFF, PNG, JPG, and EXR.

Instructions

Export the current frame (full resolution) as a still image file (.dpx, .tif, .png, .jpg, .exr...).

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": {
      "path": "<path>"
    },
    "name": "export_current_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-to-local-disk profile is partly covered. The description adds the useful facts that the frame is exported at full resolution and which formats are possible, but says nothing about overwrite behavior, directory creation, or failure modes when writing the file.

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?

One sentence, front-loaded with the verb and resource, with the format list as an efficient trailing parenthetical. Nothing is redundant and nothing could be cut without losing information.

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?

Given a one-parameter tool with no output schema and annotations covering the safety profile, the definition is close to complete: resolution, output kind, and the range of formats are all stated. The only real gap, file-vs-directory semantics of `path`, is minor at this complexity.

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

Parameters3/5

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

Schema description coverage for the single `path` parameter is 0%, so the description carries the burden. The format list implicitly tells the agent that the file extension selects the output format, which is genuinely useful meaning beyond the schema, but the description never states whether `path` is a full file path or a directory, or whether the extension is mandatory.

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?

The description gives a specific verb ('Export'), a specific resource ('the current frame'), and a scope qualifier ('full resolution'), followed by an enumeration of output formats. That distinguishes it from the sibling get_current_frame_thumbnail by implication, though the contrast is never stated explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when to pick this over quick_export, export_timeline, or get_current_frame_thumbnail, nor are preconditions such as an open project or a positioned playhead mentioned. The agent must infer all routing from the tool name.

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