Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_css_beautifier

Read-onlyIdempotent

Beautify minified or messy CSS by re-indenting, adjusting spacing, and optionally sorting properties. Get readable CSS with configurable formatting options.

Instructions

CSS Beautifier. Pretty-print and re-indent minified or messy CSS with configurable indent size and type (spaces or tabs), brace/colon spacing, blank lines between rules, comment preservation, alphabetical property sorting, and a final-newline toggle. Use it to make CSS readable; use webdev_css_minifier for the inverse (strip whitespace to shrink for production), and webdev_code_formatter when you need HTML, CSS, or JS handled in one multi-language pass. Runs locally via a Node bridge on the CSS you provide: read-only, non-destructive, idempotent, offline, contacts no external service, and is rate-limited (anonymous 60/min, 500/hr, 2000/day). Returns the beautified CSS plus original/beautified byte sizes and the size-change delta and percentage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssYesThe CSS source to beautify. Must be non-empty.
indentSizeNoSpaces per indent level; ignored when indentType is "tabs".
indentTypeNoIndent with spaces or a tab character.spaces
newlineBeforeRuleNoInsert a blank line before each selector and comment block.
newlineAfterRuleNoPut the opening brace and closing brace on their own lines.
newlineBeforePropertyNoIndent each declaration on its own line.
spaceAfterColonNoAdd a space after the colon in each declaration.
spaceBeforeBraceNoAdd a space between the selector and the opening brace.
preserveCommentsNoKeep CSS comments; when false they are dropped.
sortPropertiesNoSort declarations alphabetically within each rule.
insertFinalNewlineNoEnsure the output ends with a trailing newline.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
originalNoThe original CSS, trimmed and echoed back.
beautifiedNoThe formatted, re-indented CSS.
originalSizeNoOriginal CSS length in characters.
beautifiedSizeNoBeautified CSS length in characters.
sizeChangeNobeautifiedSize minus originalSize (negative when smaller).
changePercentageNoPercent size change relative to the original (2-decimal rounded).
optionsNoThe normalized options actually applied (defaults filled in).
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds key operational traits: runs locally via Node bridge, offline, rate-limited (60/min, 500/hr, 2000/day), non-destructive, idempotent. Also describes return value (sizes and delta). 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.

Conciseness4/5

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

Single well-structured paragraph: starts with tool purpose, then sibling differentiation, then behavioral notes, then return info. Dense but not verbose given 11 parameters and multiple siblings. Could be slightly shorter but earns its place.

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?

Covers purpose, usage vs siblings, behavioral traits (local, rate limits), and return value. With output schema present, no need to detail return structure. Schema covers parameters. Minor gap: does not explicitly mention that it works on CSS strings only (but schema required field 'css' makes it obvious).

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 covers all 11 parameters with 100% description coverage. The description offers a high-level summary of options (indent size/type, spacing, comments, sorting, newline) but adds no detail beyond the schema. Baseline 3 is appropriate.

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?

Clearly states 'CSS Beautifier' with verb 'Pretty-print and re-indent' and resource 'minified or messy CSS'. Explicitly distinguishes from siblings: webdev_css_minifier for minification and webdev_code_formatter for multi-language formatting.

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?

Explicitly provides when-to-use ('make CSS readable') and when-not-to-use ('use webdev_css_minifier for the inverse, webdev_code_formatter for multi-language'). Gives direct alternative tools.

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