Skip to main content
Glama

edit_highlight

Apply ordered, all-or-nothing operations to a highlight—trim, split, reorder, set POV/speed/captions, and update metadata—before rendering the revised video.

Instructions

Edit a highlight with a list of operations applied in order (all-or-nothing). Operations: trim{segment,start_delta_s,end_delta_s} · set_range{segment,start_tick,end_tick} · set_pov{segment|null,steamid} · set_speed{segment|null,speed} · set_caption{segment,caption} · add_segment{start_tick,end_tick,pov_steamid,speed,caption,index} · remove_segment{segment} · move_segment{segment,to} · split_segment{segment,at_tick} · set_meta{title,description,tags}. Segment indexes are 0-based. Example slow-motion on the last second of segment 0 that ends at tick 5000: [{op:'split_segment',segment:0,at_tick:4936},{op:'set_speed',segment:1,speed:0.5}]. Call render_highlight afterwards to produce the new video.

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": {
      "highlight_id": "<highlight_id>",
      "ops": "<ops>"
    },
    "name": "edit_highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
opsYes
highlight_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic flags (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds the non-obvious transactional contract ("all-or-nothing"), the ordering guarantee, and the downstream render dependency, none of which are expressible in annotations. These are exactly the behavioral facts an agent needs before composing a multi-op batch.

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?

Front-loaded with the verb, resource and atomicity guarantee, then a compact op catalog, then a worked example, then the next step — a logical order with no filler. The op catalog is terse to the point of being cipher-like, but the notation is consistent and the example disambiguates it.

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 complex batch-mutation tool with ten polymorphic operation shapes, the description covers what an agent must know: the operation set, ordering, atomicity, index base, and the required follow-up render. Return values are covered by the output schema, so no further explanation is owed.

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?

With schema description coverage reported at 0%, the description carries the burden and largely does: it enumerates all ten operation names with their field sets, states that segment indexes are 0-based, and notes which ops accept segment|null. It does not explain highlight_id or the meaning of index/to beyond their names, and the field bullets restate schema property names rather than adding semantics.

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 ("Edit a highlight") plus the core mechanism ("a list of operations applied in order"), immediately separating it from create_highlight/delete_highlight. It also names the sibling it hands off to ("Call render_highlight afterwards"), so an agent can place it in the workflow without opening a schema.

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?

Gives clear sequencing guidance: edits are applied in order, are all-or-nothing, and a render_highlight call is required afterwards to produce the new video. It does not state exclusions (e.g. when to prefer create_highlight or what to do if the highlight is currently rendering), so it falls short of full when/when-not coverage.

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