Skip to main content
Glama

manage_mattes

List, add, or delete clip mattes and list or add stand-alone timeline mattes in a bin, with optional clip and stereo-eye targeting.

Instructions

Clip mattes (attached to a clip) and timeline mattes (stand-alone, in a bin).

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": {
      "action": "<action>"
    },
    "name": "manage_mattes"
  }
}

Input Schema

NameRequiredDescriptionDefault
binNo
clipNo
pathsNo
actionYes
stereo_eyeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this writes but is told it is non-destructive. The description neither confirms nor warns that the delete_clip action removes mattes, nor does it mention permission needs or what a delete affects. It adds essentially no behavioral context beyond the annotations.

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

Conciseness3/5

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

It is only one short fragment with no padding, so nothing is wasted, but it is under-specified rather than concise. Being a parenthetical appositive rather than a sentence, it does not front-load the operation the agent needs first.

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, action-dispatching mutation tool with zero schema descriptions and no output schema, the definition is far too thin. An agent cannot tell which parameters are required for which action, or what the tool returns, without inspecting the schema and guessing the mapping.

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 coverage is 0%, so the description must carry the parameter burden and largely does not. It does imply that 'clip' applies to clip mattes and 'bin' to timeline mattes, which is real added meaning, but paths, stereo_eye, and the five action values are entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (mattes) and usefully splits it into two kinds: clip mattes attached to a clip and timeline mattes standing alone in a bin. However, it is a noun phrase with no verb, so it never says what 'manage' means (list, add, delete) even though the action enum contains those operations.

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?

There is no guidance on when to use this tool, no prerequisites (e.g. a project must be open), and no mention of how it relates to siblings such as delete_clips or manage_color_group. The only implicit routing cue is the clip-vs-timeline distinction, which the agent must infer.

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