Skip to main content
Glama

Export for Platform

export_preset
Destructive

Encode a source video into platform-ready H.264 with the named platform's aspect, fps, bitrate, faststart, and pad/crop settings.

Instructions

Encode a platform-ready H.264 file (aspect, fps, bitrate, faststart) for a named platform.

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": {
      "input": "<input>",
      "platform": "<platform>"
    },
    "name": "export_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoFit to the platform aspect: pad (default) or crop.
inputYesPath to the source video.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
platformYesSets aspect, size, fps, bitrate. steam_trailer: 1080p 5.5 Mbps CBR, -14 LUFS. vertical_reel: 1080x1920 over a blurred copy of itself, -14 LUFS (ignores fit).
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.47.0
    • changedInput schema / properties / fit / description
      Previous value: -"How to fit the source into the platform aspect: pad (default) or crop."New value: +"Fit to the platform aspect: pad (default) or crop."
    • changedInput schema / properties / platform / description
      Previous value: -"Target platform. Sets aspect, resolution, fps, and bitrate. steam_trailer: 1920x1080, H.264 High, padded 5.5 Mbps CBR, AAC 48 kHz at -14 LUFS. vertical_reel: 1080x1920 with the footage centred over a blurred copy of itself, audio at -14 LUFS (fit is ignored)."New value: +"Sets aspect, size, fps, bitrate. steam_trailer: 1080p 5.5 Mbps CBR, -14 LUFS. vertical_reel: 1080x1920 over a blurred copy of itself, -14 LUFS (ignores fit)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds useful encoding traits (aspect, fps, bitrate, faststart) but says nothing about whether an existing output file gets replaced or where files land, which is the destructive behavior an agent should be warned about.

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?

A single tight sentence that front-loads the verb and the output format. Nothing redundant or padded.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and every parameter is documented in the schema. However, for a tool flagged destructive with an overwrite option, the description should mention the overwrite/replacement behavior and output location to be fully complete.

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 is 100%, so the enum semantics for platform, fit, output, and overwrite are fully documented in structured data. The description only reiterates the platform-driven settings (aspect, fps, bitrate) already present in the schema, adding no new meaning.

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?

Specific verb (encode) plus resource (platform-ready H.264 file) and scope (a named platform), so the agent knows exactly what the tool produces. It doesn't distinguish itself from nearby siblings like export_gif or compress, which leaves some ambiguity about which export path to take.

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?

The description offers no when-to-use conditions and never mentions alternatives such as compress, convert, or export_gif. The only implied usage is that the platform parameter drives the settings, which the schema already states.

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