Skip to main content
Glama

remove_audio

Strip the audio track from a video to generate a silent version for editing, publishing, or reuse.

Instructions

The same video without sound.

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

Input Schema

NameRequiredDescriptionDefault
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it does not say whether the source video is modified or a new asset is produced, whether the output format/source is preserved, or what happens to the removed audio. For a media transformation tool this leaves the mutation behavior under-specified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but it is short to the point of being a fragment with no subject or verb. There is no front-loaded statement of what the tool returns, and the single sentence conveys almost no actionable information.

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?

With one required, undocumented parameter, no output schema, and only partial annotation coverage, the description carries most of the explanatory burden and delivers almost none of it. An agent knows the general idea but not the input format, the return value, or whether the original asset survives.

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?

Schema description coverage is 0% for the single required 'video' parameter, so the description must compensate and does not. It never clarifies whether 'video' is a file path, URL, asset ID, or previously built video reference — the one thing an agent most needs to invoke this correctly.

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

Purpose2/5

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

"The same video without sound" is a noun phrase that essentially restates the tool name rather than stating an action. It implies a media transformation but never says whether the tool renders a new video file, strips the audio track, or returns a reference. An agent can guess the intent but cannot confirm the operation or distinguish it from the sibling extract_audio.

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?

There is no when-to-use guidance, no prerequisites, and no exclusions. Nothing routes the agent between this and extract_audio or the other video-mutating siblings. The only implicit signal is the tool name itself.

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