Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_js_minifier

Read-onlyIdempotent

Minify JavaScript code by stripping comments and whitespace, mangling variable names, and optionally removing console and debugger statements to shrink file size for production.

Instructions

JavaScript Code Minifier. Minify a JavaScript snippet to shrink file size by stripping comments, collapsing whitespace, and optionally removing console/debugger statements, mangling variable names, and dropping unused code. Use this for production deployment when you only need a smaller file; use webdev_js_obfuscator instead to actively hide logic with string encoding and control-flow flattening, or webdev_javascript_beautifier to reverse compaction and re-indent. Regex-based transform, not a full parser, so output is not guaranteed runnable and is not reversible: keep the original source. Runs locally via a Node bridge: read-only, non-destructive, contacts no external service, rate-limited (60 requests per minute for anonymous callers). Returns the minified code, applied options, before/after size and line statistics, and a per-step optimization report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesJavaScript source to minify. Required and non-empty (the alias input is also accepted).
levelNoMinification preset. basic does whitespace and comment stripping only; standard adds variable mangling; aggressive also removes unused code. Unknown values fall back to standard.standard
removeCommentsNoStrip block and line comments.
removeConsoleNoRemove console log, info, warn, error, and debug calls.
removeDebuggerNoRemove debugger statements.
mangleVariablesNoRename local variables to short names. Defaults to true unless level is basic.
removeUnusedCodeNoDrop empty functions and dead code after return. Defaults to true only when level is aggressive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoOriginal JavaScript source.
outputNoMinified JavaScript.
levelNoEffective level applied (basic, standard, or aggressive).
optionsNoResolved boolean flags actually applied (removeComments, removeConsole, removeDebugger, mangleVariables, removeUnusedCode).
statisticsNoSize metrics: originalSize, minifiedSize, originalLines, minifiedLines, bytesSaved, and compressionRatio percent.
optimizationReportNoPer-step entries, each with a type (success, info, or warning) and a message string.
Behavior5/5

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

The description adds significant behavioral context beyond annotations, including local execution via Node bridge, read-only and non-destructive nature, no external service contact, rate limiting, and irreversibility warning. No contradiction with annotations.

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 concise (4-5 sentences), well-structured, and front-loaded with the core purpose, followed by details and caveats. Every sentence provides useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, output schema), the description covers purpose, usage, behavior, parameters, limitations, and output content, making it complete for an agent to understand and invoke correctly.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining level presets and mentioning the 'input' alias, but the schema already describes parameters well.

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 purpose as a JavaScript code minifier that shrinks file size through specific operations, and explicitly distinguishes it from siblings (obfuscator and beautifier).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool (production deployment for smaller file) and when to use alternatives (obfuscator for hiding logic, beautifier for reversing), along with important caveats about non-guaranteed runnability.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server