Skip to main content
Glama

add_logo

Overlay a logo or watermark onto a video and adjust position, scale, and opacity to brand clips before export.

Instructions

A logo or watermark (a picture file, PNG with transparency is best). position: top-right | top-left | bottom-right | bottom-left | center. scale = its width as part of the video's width.

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": {
      "video": "<video>",
      "image": "<image>"
    },
    "name": "add_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes
scaleNo
videoYes
opacityNo
positionNotop-right

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a non-destructive, non-read-only mutation, and the description adds useful behavior about PNG transparency and how scale relates to video width. However, it does not explain whether the original video is modified or a new output is produced, what the video identifier should be, or what opacity controls.

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 definition is compact and front-loads the core image concept with no filler. The compressed fragment structure makes some parameter notes feel appended rather than clearly organized, but it is not verbose.

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 five-parameter mutation tool with no output schema and zero schema descriptions, it explains enough to make a basic call but omits opacity and video semantics and gives no usage or outcome context. Annotations reduce the safety gap, leaving the definition adequate but not complete.

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 supplies semantics for image, position (including allowed values), and scale. It leaves video and opacity completely undocumented, so it only partially compensates for the coverage gap.

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 as a logo or watermark image and mentions placement relative to a video, but it is a noun fragment rather than a clear verb+resource statement. It does not explicitly say it overlays/adds the logo to the video or distinguish itself from sibling overlay tools.

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?

It gives a format recommendation (PNG with transparency) and lists allowed position values, but provides no guidance on when to use this tool versus alternatives like add_text. It also omits prerequisites, exclusions, or context for selecting a logo overlay.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.