Skip to main content
Glama
Sign In
agent-video-engine

agent-video-engine

by ferdy252
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

transcript_import

Import source-timed transcript words from local JSON to reuse existing transcripts and avoid retranscription. Supports word arrays or native speech-recognition output.

Instructions

Import source-timed transcript words from local JSON, including a word array or native speech-recognition output. Reuses existing transcripts without retranscription.

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": {
      "projectDir": "<projectDir>",
      "expectedRevision": "<expectedRevision>",
      "assetId": "<assetId>",
      "path": "<path>"
    },
    "name": "transcript_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
assetIdYes
projectDirYesAbsolute path of the local video project directory
expectedRevisionYesRevision returned by project_inspect. Prevents overwriting newer edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a non-readonly, non-destructive, non-open-world operation. The description adds that existing transcripts are reused rather than regenerated, but it does not explain overwrite behavior, required permissions, or failure conditions beyond what the schema implies with expectedRevision.

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?

The description is two front-loaded sentences with no obvious filler, and the key differentiation appears in the second sentence. It is appropriately sized for a tool definition, though it could be slightly more explicit without becoming bloated.

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 four-parameter import tool with no output schema, the description covers the high-level purpose and input formats but not parameter semantics or operational constraints. The schema supplies some parameter detail, so the description is adequate but not complete.

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?

The description does not mention any of the four parameters by name or clarify what path, assetId, or expectedRevision mean in context. With only 50% schema description coverage, it leaves meaningful gaps for path and assetId unaddressed.

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

Purpose5/5

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

The description uses a specific verb ("Import") and resource ("source-timed transcript words") and names the accepted input forms (local JSON, word array, native speech-recognition output). The second sentence distinguishes it from the sibling transcribe tool by stating it reuses existing transcripts without retranscription.

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?

It implies when to use the tool by emphasizing reuse without retranscription, but it does not explicitly name transcribe as the alternative or state when not to use this tool. The guidance is useful but incomplete.

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