Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_css_gradient_generator

Read-onlyIdempotent

Generate a CSS gradient declaration from an ordered list of color stops. Choose linear, radial, or conic type, set direction or angle, and get ready-to-paste CSS plus usage snippets.

Instructions

CSS Gradient Generator. Build a ready-to-paste CSS gradient from an ordered list of color stops and return the full background declaration plus copy-ready usage snippets. Supports three gradient functions selected by type: linear (with a named direction like 'to right' or a custom angle), radial (circle or ellipse shape), and conic (swept from a starting angle); set repeating to emit the repeating-* variant. Use webdev_css_filter_generator instead for blur/brightness/contrast filter effects, and webdev_color_palette or webdev_hex_color to pick the colors before composing them here. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the CSS declaration string, an HTML preview snippet, the echoed gradient settings, and CSS/inline/SCSS/Tailwind usage examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoGradient function to generate.linear
directionNoFor linear, a named/keyword direction such as 'to right' or 'to bottom left'; pass 'custom' (or a value ending in deg) to drive the gradient by the angle field instead. For radial, 'circle' selects a circular shape and any other value yields an ellipse. Ignored for conic.to right
angleNoAngle in degrees. Used as the linear-gradient angle when direction is custom, and as the conic-gradient starting angle (from Ndeg). Ignored otherwise.
colorsYesOrdered color stops; at least one is required (empty returns HTTP 400).
repeatingNoWhen true, emit the repeating-* gradient variant (repeating-linear/radial/conic-gradient).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssNoFull CSS declaration, e.g. background: linear-gradient(to right, #22d3ee 0%, #a3e635 100%);
previewHtmlNoA self-contained div HTML snippet with the gradient applied inline, for live preview.
usageExamplesNoCopy-ready snippets keyed by format (css, inline, sass, tailwind), each with a title and code.
typeNoEchoed gradient type (linear, radial, or conic).
directionNoEchoed direction/shape value.
angleNoEchoed angle in degrees.
colorsNoEchoed color stops, each an object with color and optional position.
repeatingNoEchoed repeating flag.
Behavior5/5

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

Annotations indicate read-only, non-destructive, idempotent. Description adds local execution, rate limiting, and reinforces non-destructive nature. No contradictions.

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?

Description is concise (4 sentences) and front-loaded with purpose and key details. Every sentence adds value 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 complex parameters and output schema existence, description covers return values (CSS declaration, preview, settings, examples) and usage context thoroughly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions. Description adds context like required length, defaults, and ignored fields, enhancing understanding beyond schema.

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 specifies the tool generates CSS gradients from color stops, returning background declarations and snippets. It differentiates from siblings like webdev_css_filter_generator and webdev_color_palette.

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?

It explicitly states when to use alternatives: filter effects (webdev_css_filter_generator) and color picking (webdev_color_palette/webdev_hex_color), and that it runs locally without external services.

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