Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_favicon_generator

Read-onlyIdempotent

Generate a complete favicon bundle including PNG set, ICO, apple-touch-icon, webmanifest, and HTML tags from text, emoji, initials, or uploaded image.

Instructions

Favicon Bundle Generator. Render a complete favicon bundle from text, an emoji, two-letter initials, or an uploaded base64 image data URI, returning the multi-size PNG set, a multi-resolution favicon.ico, an apple-touch-icon, a site.webmanifest, ready-to-paste HTML link tags, and a downloadable ZIP. Use this to produce browser tab and home-screen icons; for embedding a single image as a data URI use webdev_base64_image_encoder, and to shrink SVG artwork first use webdev_svg_optimizer. Runs server-side on the input you provide (GD image rendering only): read-only, non-destructive, contacts no external service, caps uploads at 4 MB, and is rate-limited (30 requests/minute for anonymous callers). Returns every generated file base64-encoded plus the resolved metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faviconTypeNoSource of the icon glyph. text/initials draw textContent (initials force upper-case), emoji draws emojiContent, upload rasterizes imageDataUrl. Invalid values fall back to initials.initials
textContentNoText or initials drawn when faviconType is text or initials. Truncated to 8 characters; font shrinks as length grows. Defaults to AB.
emojiContentNoSingle emoji drawn when faviconType is emoji. Defaults to a rocket glyph.
backgroundColorNoIcon background as a 3- or 6-digit hex color (for example 4338ca). Ignored when transparentBackground is true. Defaults to 4338ca.
textColorNoGlyph color as a 3- or 6-digit hex color. Defaults to ffffff.
shapeNoIcon outline shape. Non-square shapes mask the corners to transparency.rounded
fontFamilyNoCSS font stack hint for text glyphs; unrecognized values fall back to Arial.Arial, sans-serif
sizesNoPixel sizes of PNG icons to emit (deduped and sorted). Out-of-range values are dropped. Defaults to 16, 32, 48, 64, 180, 192, 512. 16/32/48 always feed the .ico, 180 the apple-touch-icon, 192/512 the manifest.
imageDataUrlNoSource artwork for faviconType upload as a base64 data URI (png, jpeg, gif, webp, or svg+xml; SVG needs Imagick). Required for the upload type; max 4 MB decoded.
imageFitNoHow an uploaded image is scaled into the square canvas.contain
transparentBackgroundNoWhen true, omit the background fill and keep the canvas transparent.
paddingNoInner padding as a fraction of icon size (clamped 0 to 0.4).
siteNameNoApplication name written into site.webmanifest. Falls back to tabTitle then Your Website.
tabTitleNoPage title used in the generated preview HTML; also the manifest name fallback. Defaults to Your Website.
themeColorNotheme-color meta and manifest theme as a 6-digit hex color. Defaults to backgroundColor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether generation succeeded.
resultNoThe generated bundle.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds rich behavioral context: runs server-side, read-only, non-destructive, contacts no external service, upload cap 4 MB, rate-limited (30 req/min for anonymous). Also details internal behavior like truncation, font scaling, fallbacks. 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 paragraph of about 5 sentences. Front-loaded with main purpose and outputs. Dense but clear; could benefit from slight structural separation (e.g., bullet points), but remains concise and efficient.

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 15 parameters, 0 required, and presence of output schema, description covers all necessary aspects: input types, output format (base64-encoded files + metadata), constraints (size, rate limits), and fallback behaviors. No gaps identified.

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% with full parameter descriptions. Description adds extra context: e.g., initials force upper-case, font shrinks as length grows, defaults for various fields, relationships like sizes roles in .ico/apple-touch-icon/manifest. This goes beyond schema, justifying above baseline.

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?

Description clearly states it generates a favicon bundle from text, emoji, initials, or upload. Lists specific outputs: multi-size PNG set, favicon.ico, apple-touch-icon, site.webmanifest, HTML tags, and downloadable ZIP. Explicitly distinguishes from sibling tools webdev_base64_image_encoder and webdev_svg_optimizer.

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 states when to use: 'Use this to produce browser tab and home-screen icons'. Also provides clear alternatives: 'for embedding a single image as a data URI use webdev_base64_image_encoder, and to shrink SVG artwork first use webdev_svg_optimizer'.

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