Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Set export settings

set_export_settings

[write] Set the frame and the export settings. The frame is 9:16, 16:9 or 1:1 and every clip is fitted into it; the export takes format, frame rate, resolution, quality, background colour and loudness. Only passed fields change, and the frame shows at once. Use before the person exports, or when the deliverable's shape changes, then reframe clips with set_clip_transform. Not for rendering a motion graphic (use render_asset). Returns ok, aspectRatio, format, fps, resolution, quality, backgroundColor, loudness. Related: set_clip_transform, align_clip, set_canvas_aspect_ratio. Full docs: load_skill with tools: [name].

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": {
      "project_id": "<project_id>"
    },
    "name": "set_export_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoExport frame rate.
formatNoExport file type.
qualityNoExport quality.
loudnessNoThe export's sound: off plays it as mixed; social brings it to the social apps' loudness, peaks kept clear.
project_idYesThe AskEditor project this acts on (from list_projects).
resolutionNoExport size.
aspectRatioNoThe frame every clip is fitted into.
backgroundColorNoBehind the clips, #rrggbb.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing patch semantics ("Only passed fields change") and immediate visibility ("the frame shows at once") — neither is derivable from readOnlyHint/destructiveHint/idempotentHint. It stops short of saying whether an already-rendered export is invalidated or whether the preview change requires a re-export, which is the main remaining unknown.

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?

One dense, front-loaded paragraph that leads with the write marker and the action, then branches to state/usage/return values. The enumerated return list and the "Related:" roster are mildly padding-like given no output schema exists, but they serve discovery; nothing is redundant.

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

Completeness4/5

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

Covers purpose, patch semantics, sequencing with set_clip_transform, a returns list standing in for a missing output schema, and a docs pointer via load_skill. Adequate for an 8-parameter mutation with full annotation coverage; the only gap is the relationship to export_video / whether settings affect an in-flight export.

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%, so baseline is 3; the description earns above baseline by explaining the aspectRatio parameter's downstream effect ("every clip is fitted into it") and by grouping the export fields, which tells the agent these travel together as one deliverable shape. Enum values themselves are left to the schema, which is appropriate.

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 ("Set the frame and the export settings") and enumerates exactly which settings move (format, frame rate, resolution, quality, background colour, loudness). It also carves out the sibling boundary explicitly with "Not for rendering a motion graphic (use render_asset)", so an agent can distinguish it from render_asset and export_video without opening another schema.

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

Usage Guidelines5/5

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

Gives concrete timing ("Use before the person exports, or when the deliverable's shape changes") plus the follow-up step ("then reframe clips with set_clip_transform"). It also names the exclusion and the alternative tool for it, which is the strongest form of routing guidance.

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

All AskEditor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources