Skip to main content
Glama

set_clip_mark_in_out

Set or clear a media pool clip's mark in and out points in source frames, with options for video, audio, or all marks.

Instructions

Set (or clear) a media pool clip's mark in/out, in source frames.

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": {
      "clip": "<clip>"
    },
    "name": "set_clip_mark_in_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
clearNo
mark_inNo
mark_outNo
mark_typeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive mutation confined to the local app. The description adds that marks are expressed in source frames, which is useful, but it does not explain the interaction between the clear flag and null mark_in/mark_out values or what happens to unspecified marks.

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?

A single front-loaded sentence with no wasted wording. It is efficient, though its brevity leaves several behavioral details unstated.

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

Completeness2/5

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

For a five-parameter mutation tool with zero schema description coverage and no output schema, one sentence is too thin. An agent cannot tell how mark_type, clear, and null values interact, or what the clip parameter expects.

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 description coverage is 0%, so the description must compensate. It adds unit meaning to mark_in/mark_out ('in source frames') and hints at the clear behavior, but leaves mark_type (video/audio/all), null-vs-clear semantics, and the clip identifier format unexplained.

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+resource: set or clear a media pool clip's mark in/out. 'Media pool clip' implicitly distinguishes it from the sibling set_timeline_mark_in_out, though no alternative is explicitly named.

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 '(or clear)' hints that the tool handles both setting and clearing marks, but there is no explicit when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as set_timeline_mark_in_out.

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

Deploy Server

Other Tools