Skip to main content
Glama

clips_link

Link or unlink timeline clips to control whether video and audio move together, such as moving video without its audio.

Instructions

Link or unlink timeline clips (e.g. to move video without its audio).

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": {
      "clips": "<clips>"
    },
    "name": "clips_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
linkedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/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 says what linking does conceptually but not whether the operation is reversible, what happens to existing links when re-linking, whether it requires an active selection or open sequence, or what is returned. For a mutation tool with zero annotation coverage this is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the verb first and an illustrative example appended; nothing is wasted and nothing is buried. Length is well matched to the amount of information conveyed.

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 two-parameter mutation tool with no annotations, no output schema, and an entirely undocumented clips argument, the description leaves too much for the agent to guess. It should at minimum describe the accepted clips value and confirm the effect of the linked flag.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the 'clips' property has no type or description at all, so the description must compensate and does not. Only indirectly does 'link or unlink' hint that 'linked' toggles direction (default true), and nothing explains the shape of the clips argument (single clip, ID, or list).

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 pair (link/unlink) and a specific resource (timeline clips), plus a concrete parenthetical example of the resulting behavior. It is clear what the tool does, though it stops short of differentiating itself from the sibling media_link.

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 'e.g. to move video without its audio' implies the typical use case, which is genuinely helpful context. However, there is no explicit statement of when to prefer this over media_link or clip_update, and no stated preconditions such as needing clips already selected on the timeline.

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