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

agent-video-engine

by ferdy252
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

media_add

Probe and reference a local original image, video, or audio file without copying it, and optionally append video or audio to the project timeline.

Instructions

Probe and reference a local original image, video or audio file without copying it. Optionally append video/audio to the main timeline.

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>",
      "path": "<path>"
    },
    "name": "media_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
projectDirYesAbsolute path of the local video project directory
addToTimelineNo
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 declare it as a non-read-only, non-destructive, closed-world operation. The description adds one genuinely useful behavioral detail — the file is referenced in place rather than copied — but says nothing about what project state changes, how media IDs are produced, or failure modes, which matters for a mutating tool.

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?

Two short sentences, front-loaded with the core action and followed by the optional behavior. No redundant wording.

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

Completeness4/5

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

Given only four parameters, no output schema, and annotations covering the safety profile, the definition covers enough for correct invocation. The main omission is what the tool returns (e.g., a media reference/ID) that downstream tools like media_index_get would consume.

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

Parameters4/5

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

Schema coverage is only 50%, but the description compensates for the two undocumented parameters: 'path' is implicitly the local original file, and 'addToTimeline' is explained as the optional timeline append. The remaining required parameters are documented in the schema itself.

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 set ('Probe and reference') and resource ('local original image, video or audio file') plus an optional side effect (timeline append). It is distinguishable from sibling media_relink by the 'without copying it' framing, though it does not explicitly contrast with media_index/media_search.

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?

No explicit when-to-use or when-not-to-use guidance. The 'Optionally append video/audio to the main timeline' clause hints at one scenario, but the description never tells the agent when to pick this over media_index, media_search, or media_relink.

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