Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Video Blur Region

video_blur_region
Destructive

Pixelates/blurs one or more rectangles over the video — the tool for redacting PII (an email pane, a name) before publishing a screen recording. Rects are in source pixels, top-left origin: [{x,y,w,h, start_ms?, end_ms?}] — omit the times to cover the whole clip. Great with a marker timeline's bounds. Returns the output path.

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source video file.
outputNoDefault: <input>_blurred.mov. Missing parent folders are created.
confirmNoIgnored; kept for older clients.
regionsYes[{x,y,w,h, start_ms?, end_ms?}] in source pixels (top-left).
overwriteNoReplace an existing file at output. Without it an existing output is refused. The input is never overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to write the output. Without it the call returns a preview and writes nothing."New value: +"Ignored; kept for older clients."
  2. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to write the output. Without it the call returns a preview and writes nothing.",
+  "type": "boolean"
+}
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Replace an existing file at output. Without it an existing output is refused. The input is never overwritten.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / output / description
      Previous value: -"Default: <input>_blurred.mov"New value: +"Default: <input>_blurred.mov. Missing parent folders are created."
  4. Changed1 schema field changed
    • addedInput schema / properties / input / description
      Added value: +"Path to the source video file."
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds useful behavior beyond that: source-pixel coordinate space, top-left origin, and that omitting start_ms/end_ms covers the whole clip. It also names the return value (output path). It does not discuss re-encoding/quality impact or the overwrite refusal behavior, which lives only in the schema.

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?

Three compact sentences, purpose front-loaded, with coordinate format and time-omission rule packed without waste. Nothing is restated for filler.

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?

For a mutation tool with no output schema, the description covers purpose, coordinate semantics, temporal scoping, and the return value (output path). Missing only secondary details such as re-encode implications or whether audio is preserved.

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 100%, so the baseline is 3, but the description adds real semantics: region coordinates are in source pixels with top-left origin and optional time bounds where omission means full-clip coverage. That goes beyond the schema's terse region description.

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?

States a specific verb (pixelates/blurs) and resource (rectangles over a video) plus the concrete intent (redacting PII before publishing). It is clearly distinguishable from siblings like video_trim, video_concat, and video_reframe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear use context ('redacting PII ... before publishing a screen recording') and hints at a companion workflow ('great with a marker timeline's `bounds`'). It does not explicitly name sibling alternatives or state when not to use it, so it stops short of full routing guidance.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources