Skip to main content
Glama

style_save

Save your editing preferences as a named style and reuse it in timelines so future edits automatically match your chosen look, transitions, captions, and audio settings.

Instructions

Save the user's editing preferences as a named style (look, transition, autoPunch, captions, sfxOnTransitions, hook, removeSilences, music volume, notes). Use it in timelines as "style": "" so every future edit matches.

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": {
      "style": "<style>"
    },
    "name": "style_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the saved style persists and drives all future edits, which is meaningful consequence information. It does not disclose whether calling again with the same name overwrites, where the style is scoped (user vs project), whether the id is generated server-side or must be supplied, or what the call returns.

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?

Two compact sentences, front-loaded with the action and its field list, then the consumption pattern. The parenthetical field enumeration is dense but earns its place given the free-form schema. No filler or redundant restatement of the tool name.

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 one-parameter write tool with no annotations, no output schema, and a schema that declares no inner properties, the description covers the field vocabulary and the downstream reference syntax. It is still incomplete on the points an agent needs to call it correctly on the first try: how the name is specified, overwrite semantics, and whether an id is returned.

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 coverage is 0% for a single free-form nested object with no declared properties, so the description must compensate — and it does partially by enumerating eight expected inner fields. It still leaves the most important ambiguity unresolved: the tool claims to save a *named* style, yet the description never says whether the name is a key inside the "style" object or generated automatically and returned.

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?

States a specific verb and resource: "Save the user's editing preferences as a named style", and enumerates the preference categories covered (look, transition, autoPunch, captions, sfxOnTransitions, hook, removeSilences, music volume, notes). An agent immediately knows this is a persistence tool for edit settings. It lacks any explicit differentiation from a hypothetical style-listing or style-applying sibling, but no such sibling is present in the catalog.

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 second sentence supplies real downstream usage context: reference the result in timelines as "style": "<id>" so future edits match. That is genuinely useful for understanding why you would call it. However, there is no guidance on when not to call it, whether an existing style name is overwritten, or what prerequisites (project context, existing style id) apply.

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