Skip to main content
Glama

manage_takes

Manage timeline item takes by listing, adding clips with optional source ranges, selecting or deleting by 1-based index, and finalizing the chosen take.

Instructions

Take selector on a timeline item: list takes, add a clip as a take (optional source range), select / delete a take by 1-based index, or finalize the selected take.

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

Input Schema

NameRequiredDescriptionDefault
endNo
clipNo
itemYes
indexNo
startNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations declare destructiveHint=false, yet the description advertises a "delete a take" action, which is an operation an agent would reasonably treat as destructive — a meaningful inconsistency. The description also never explains what "finalize" does to the take stack, whether deleted takes are recoverable, or what state the item must be in.

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 front-loaded sentence with a colon-delimited action list; every clause maps to a parameter or action and there is no filler.

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

Completeness3/5

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

For a six-parameter, multi-action tool with no output schema, the description covers the action surface but not the return of "list" (what a take record contains) or post-action state, which an agent needs to chain calls. Adequate but with clear gaps.

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?

With 0% schema description coverage the description must carry the load, and it does partially: it maps clip to add, index to select/delete, start/end to an "optional source range", and usefully states the index is 1-based. It leaves the units/format of start and end (frames vs timecode) and the clip identifier format undefined.

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?

"Take selector on a timeline item" names a specific resource and scope, and the colon-list enumerates all five operations (list, add, select, delete, finalize) with their operands. It does not differentiate itself from any sibling tool, which keeps it from 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 Guidelines3/5

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

Usage is implied by the action list — the agent can tell that add needs a clip and select/delete need an index — but nothing states when this tool is preferable to alternatives, nor whether sequential dependencies exist (e.g. add before select before finalize).

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