Skip to main content
Glama

set_format

Idempotent

Convert a whole video to horizontal 16:9 or vertical 9:16 for YouTube, Reels, Shorts or TikTok, keeping shots framed for the new shape. Returns changed IDs as one undo step.

Instructions

Make the whole video horizontal (16:9, YouTube) or vertical (9:16, Reels / Shorts / TikTok). Shots stay as they are, framed for the new shape. One undo step for the person. Returns { done } with the ids of what changed.

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": {
      "format": "<format>"
    },
    "name": "set_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYeshorizontal 16:9 or vertical 9:16.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / format / description
      Added value: +"horizontal 16:9 or vertical 9:16."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing that existing shots are untouched ('Shots stay as they are, framed for the new shape'), that the change is a single undo step, and that the call returns '{ done } with the ids of what changed'. That undo granularity and preservation guarantee are non-obvious behavior an agent would otherwise have to guess. It stops short of 5 only because 'ids of what changed' leaves the id type ambiguous and no output schema exists to clarify it.

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?

Three tight sentences: the transformation first, then the side-effect guarantee, then the return payload. Nothing is repeated from the schema and no sentence is filler.

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?

For a single-parameter tool with full schema coverage and no output schema, the description covers what happens, what is preserved, undo granularity, and roughly what is returned. Nothing an agent needs in order to call it correctly is missing.

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 100% and the enum values are already documented, so the baseline is 3. The description earns above baseline by attaching each value to a real-world target ('16:9, YouTube' vs '9:16, Reels / Shorts / TikTok'), which helps the agent pick the right value from user intent rather than from the raw strings.

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

Purpose5/5

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

States a specific verb and resource ('Make the whole video horizontal ... or vertical') and immediately clarifies the scope ('whole video') versus the per-shot tools implied by siblings like add_shot or cut_shot. It also spells out the aspect ratios and target platforms, so the agent knows exactly what transformation is performed.

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?

The parenthetical 'YouTube' and 'Reels / Shorts / TikTok' give useful intent context for choosing between the two enum values, so usage is implied. However, there is no explicit statement of when to use this versus alternatives such as set_style or camera, and no exclusions or prerequisites.

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