Skip to main content
Glama
Sign In
video-editor-mcp

video-editor-mcp

by chevrolet231X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

add_watermark

Overlay a logo or watermark image on a video, selecting corner or center position and adjusting opacity and scale.

Instructions

Overlay a logo/watermark image onto a video at a chosen corner or the center.

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": {
      "input_path": "<input_path>",
      "watermark_path": "<watermark_path>",
      "output_path": "<output_path>"
    },
    "name": "add_watermark"
  }
}

Input Schema

NameRequiredDescriptionDefault
opacityNo
positionNobottom-right
input_pathYesSource video path. Relative paths resolve against MEDIA_DIR (defaults to the server's working directory); absolute paths are used as-is.
output_pathYesDestination path. Relative paths resolve against MEDIA_DIR (defaults to the server's working directory); absolute paths are used as-is.
scale_widthNoResize the watermark to this width in pixels before overlaying
watermark_pathYesPath to the watermark/logo image. Relative paths resolve against MEDIA_DIR (defaults to the server's working directory); absolute paths are used as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only mentions the basic overlay operation. It does not mention that it creates a new output file, any format requirements, or potential side effects, leaving the agent under-informed about the tool's impact.

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?

The description is a single clear sentence with no redundant words. It is efficiently structured and immediately conveys the core operation.

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?

Given the complexity of video processing and the absence of output schema and annotations, the description is too sparse. It lacks details on output behavior, supported formats, or any caveats, making it incomplete for an AI agent to fully understand the tool's implications.

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?

Schema coverage is 67%, and the description adds slight context by mentioning position ('corner or the center'), which aligns with the position enum. However, it does not explain other parameters like opacity or scale_width, so it only marginally supplements the schema.

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?

The description clearly states the action ('Overlay') and resource ('logo/watermark image onto a video'), and specifies position options ('chosen corner or the center'). It distinguishes from sibling add_text_overlay by focusing on an image watermark, though it doesn't explicitly name the alternative.

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 guidance is provided on when to use this tool versus alternatives like add_text_overlay. The description simply states what it does without any context on suitable scenarios or exclusions.

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