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

video-editor-mcp

by chevrolet231X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

adjust_volume

Adjust a video's audio volume using a factor, with an option to mute the track entirely.

Instructions

Change the audio volume of a video, or mute it entirely.

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>",
      "output_path": "<output_path>"
    },
    "name": "adjust_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteNoSet true to remove audio entirely (ignores volume_factor)
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.
volume_factorNo1 = unchanged, 1.5 = 50% louder, 0.5 = 50% quieter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state the primary action and the mute option, which adds some transparency, but it does not mention side effects like re-encoding, overwriting, or whether the video track is preserved.

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, concise sentence that front-loads the action and includes the mute alternative. Every word earns its place with no redundancy.

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?

Given the simple nature of the tool and full schema coverage, the description is adequate but not rich. It lacks usage context, behavioral limitations, or output expectations, which would be valuable since there is no output schema or annotations.

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 100%, so the baseline is 3. The description does not add parameter semantics beyond what the schema already provides, such as volume_factor behavior or mute ignoring volume_factor, but these are already documented.

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 clearly states the tool's function: changing the audio volume of a video, with an option to mute entirely. This specific verb+resource combination distinguishes it from sibling tools like extract_audio or convert_format.

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 about when to use this tool versus its siblings, nor any mention of alternatives or prerequisites. The description implies use for volume adjustment but does not offer any contextual direction.

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