Skip to main content
Glama

Edit a clip

clipember_edit_clip

Edit a clip without opening the editor: captions on/off, caption style (a preset id), position, AI keywords and emoji; replace a phrase in the captions; delete, move or split sections (numbered from 0 in playback order); trim seconds off the start or end; remove pauses and filler words. Edits go into the clip's draft — nothing is re-rendered until you call clipember_render_clip; clipember_undo_clip reverts the last edit. The reply lists the clip's sections with their first words.

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": {
      "clipId": "<clipId>"
    },
    "name": "clipember_edit_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
captionsNo
trimEndSecNo
minPauseSecNoShortest pause to remove (default 0.5)
moveSectionNo
removePausesNo
splitSectionNoSplit a section atSec seconds after its start
trimStartSecNo
removeFillersNo
replacePhraseNo
deleteSectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the draft model: all edits stage into a draft and nothing is re-rendered until clipember_render_clip, with clipember_undo_clip as the revert path. It also describes the reply shape (sections plus their first words), which is the only source of that information since there is no output schema.

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?

Dense but disciplined: capability list first, draft/render/undo semantics second, return value last. Semi-colon chaining keeps 11 parameters in a compact block without filler sentences, though the opening sentence is long enough that a reader must parse clause by clause.

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?

For an 11-parameter, nested-object mutation tool with no output schema, the definition covers the essentials: what can be changed, that changes are staged, how to commit or revert, and what comes back. Minor gaps remain — no mention of minPauseSec's default or caution about stacking multiple section operations in one call — but 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 description coverage is only 18%, so the description has to carry meaning — and it does: it maps nearly every parameter to plain language (captions on/off, style preset id, position, keywords/emoji, phrase replacement, trim seconds off start or end, remove pauses and fillers). The standout addition is 'numbered from 0 in playback order' for sections, which the schema only encodes as a 0-199 integer range; minPauseSec and splitSection.atSec are left entirely to the schema.

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?

Opens with a specific verb+resource ('Edit a clip without opening the editor') and then enumerates the exact editable surface: captions, style preset, position, AI keywords/emoji, phrase replacement, section delete/move/split, start/end trim, pause and filler removal. That enumeration makes it unmistakable against siblings like clipember_get_clip or clipember_rename_clip_request.

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

Usage Guidelines4/5

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

Explicitly routes the agent to clipember_render_clip for materialization and clipember_undo_clip for reverting, which is real when-to-use guidance. It does not state exclusions (e.g. that it cannot change clip length beyond trimming limits or that it is not a substitute for creating a clip), so it falls short of a full when/when-not pair.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources