Skip to main content
Glama

reformat

Resizes video to 9:16, 1:1, 4:5 or 16:9 for social platforms using blur, crop or pad modes to fit the target frame without unwanted cutting.

Instructions

Changes the shape: 9:16 (Shorts, Reels, TikTok) | 1:1 | 4:5 | 16:9. mode: blur (blurred copy behind, nothing is cut off) | crop (fills the frame, cuts the sides) | pad (black bars).

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": "reformat"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoblur
shapeNo9:16
videoYes

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is already covered and the bar is lower. The description adds useful behavioral detail per mode ('nothing is cut off', 'cuts the sides'), which tells the agent about content loss. It does not say whether the source video is replaced or a new asset is produced, nor what is returned, which matters for a non-read-only tool.

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?

Compact, pipe-delimited, and front-loaded with the shape options followed by mode semantics; nearly every token carries information. The opening 'Changes the shape' is slightly elliptical (shape of what?) and the dense formatting makes it read more like an enum dump than prose.

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?

For a 3-parameter transform with no output schema, the agent still lacks the identity/format of the required 'video' input and any statement about whether output is a new clip or an in-place modification. What is covered (shape and mode vocabulary) is covered well, but the definition is not complete enough to invoke confidently without inspecting the schema.

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 description coverage is 0%, so the description carries the full burden and largely succeeds: it spells out all four shape values and all three mode values with explanatory parentheticals, adding meaning well beyond a bare string enum. The gap is the required 'video' parameter, which is never described at all (path? ID? URL?), so one third of the parameters remains undefined.

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 concrete verb ('changes the shape') and enumerates every allowed shape value with recognizable platform examples (Shorts, Reels, TikTok), so the agent knows this reformats video aspect ratio. It never names the target resource explicitly ('video') nor differentiates itself from siblings like crop_zoom, but the intent is unambiguous.

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?

There is no guidance on when to pick this tool over crop_zoom or export, and no prerequisites or ordering hints. What it does provide is choice guidance within the tool: the blur vs. crop vs. pad trade-offs (nothing cut off / cuts the sides / black bars) let the agent pick a mode intelligently. That is mode selection, not tool selection, so usage guidance remains implied only.

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