Skip to main content
Glama
gherardo200-glitch

illustrator-mcp

by gherardo200-glitch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Vectorize Image → Editable Paths

illustrator_vectorize_image

Convert raster images into editable vector paths in Illustrator using VTracer or Image Trace. Ideal for logos and flat art, reducing manual redrawing.

Instructions

Turn a raster image (PNG/JPG, e.g. AI-generated art a client sent) into editable VECTOR PATHS in Illustrator. This automates the 'redraw the artwork from scratch' task.

Engines:

  • 'vtracer' (default): open-source VTracer produces a clean SVG that is opened as editable paths. Usually cleaner than Image Trace; free and local. Needs the vtracer binary installed (see README).

  • 'image_trace': Illustrator's built-in Image Trace (no install), kept as a fallback.

Input: path (absolute) OR image_base64 (bytes / data: URI, for images pasted in chat).

VTracer args: mode ('color'|'blackwhite'), curve_mode ('spline'|'polygon'|'pixel'), filter_speckle (remove specks, higher = cleaner), color_precision (2-8), corner_threshold (deg). Image Trace args: mode, preset, max_colors, threshold, path_fidelity, corner_fidelity, noise_fidelity, expand.

Best on logos, flat art, line art, and few-color graphics. Photorealistic images produce many paths and usually need manual cleanup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoColor mode. (grayscale applies to Image Trace only).color
pathNoAbsolute path to the image file.
engineNoVectorization engine. Default 'vtracer' (free, local, cleaner).vtracer
expandNoImage Trace: expand into editable paths.
presetNoImage Trace preset name (image_trace engine).
thresholdNoImage Trace: B/W cutoff.
curve_modeNoVTracer curve fitting. 'spline' = smooth curves (default).spline
max_colorsNoImage Trace: palette size.
image_base64NoImage bytes as base64 (or data: URI). Use when there's no file on disk.
new_documentNoImage Trace: trace into a fresh RGB document.
path_fidelityNoImage Trace: Paths slider.
filter_speckleNoVTracer: discard patches smaller than N px (higher = cleaner). Default 4.
noise_fidelityNoImage Trace: Noise slider.
color_precisionNoVTracer: color detail in bits (2-8). Lower = fewer colors.
corner_fidelityNoImage Trace: Corners slider.
corner_thresholdNoVTracer: corner angle threshold in degrees. Default 60.

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that the tool creates editable vector paths, mentions dependency on vtracer binary, and explains engine behavior. It does not contradict annotations and provides useful behavioral context beyond them.

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?

The description is relatively long but well-structured with clear sections for engines, input, args, and best practices. The first sentence captures the main purpose. Each sentence adds information, though some minor redundancy could be trimmed.

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?

Given 16 parameters and no output schema, the description covers input methods, engine differences, arg categories, and usage recommendations. It explains the output (editable paths). There is no significant missing context for an agent to use the tool 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 coverage is 100% so all parameters are described. The description adds value by grouping engine-specific args, explaining default values (e.g., filter_speckle default 4), and clarifying the input options (path or base64). This enriches understanding beyond what schema alone provides.

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 'Turn a raster image ... into editable VECTOR PATHS in Illustrator.' It uses specific verbs and resource, distinguishes from siblings (no other tool does vectorization), and mentions input formats and engines.

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 explicitly states 'Best on logos, flat art, line art, and few-color graphics. Photorealistic images produce many paths and usually need manual cleanup.' It also explains the two engines and their appropriate use cases (vtracer default, image_trace fallback), providing clear when-to-use and when-not-to-use guidance.

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/gherardo200-glitch/illustrator-mcp'

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