Skip to main content
Glama

link_items

Links or unlinks timeline items, such as a video clip and its audio, so related media stays synchronized during editing.

Instructions

Link or unlink timeline items (e.g. a video clip and 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": {
      "items": "<items>"
    },
    "name": "link_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
linkedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation/safety profile is covered. The description adds the conceptual example but leaves out behavior the agent needs: whether existing links are replaced, whether unlinking (linked=false) undoes prior links, how many items can be passed, and whether the items must be on the same track.

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 filler; the parenthetical example earns its place by disambiguating "link." It is efficient, though its brevity contributes to the documentation gaps scored elsewhere.

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 0% schema coverage, no output schema, and a conceptually ambiguous sibling (link_clip_media), the description leaves too much undocumented: item identity format, required item count, and the effect of setting `linked` to false are all unstated.

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%, so the description carries the full burden for the two parameters. It only implies that a Boolean toggles link vs unlink; it never explains that the parameter is called `linked`, defaults to true, or what format the `items` array elements take (IDs, paths, names) and how many are accepted.

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?

"Link or unlink timeline items" gives a specific verb pair and resource, and the parenthetical "(e.g. a video clip and its audio)" clarifies what linking means conceptually. It does not distinguish this tool from the sibling link_clip_media, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description states no when-to-use conditions, no prerequisites (same track, adjacent items, existing sync state), and does not name link_clip_media or auto_sync_audio as the alternative for media-pair linking. An agent must guess which linking tool applies.

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