Skip to main content
Glama
lazyq666

Illustrator MCP Unified

by lazyq666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import SVG as Editable

import_svg_as_editable

Load SVG files into the active Illustrator document as editable paths, text, and groups instead of linked images. Use it to edit vector artwork directly in Illustrator.

Instructions

Import an SVG file into the active document as editable Illustrator paths/text/groups (NOT as a linked image). Internally opens the SVG as a temporary document, duplicates its contents into the target document, then closes the source. Use this instead of place_image for SVG. Runs without activating Illustrator in default background mode; never invokes Computer Use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX position of the imported content (top-left of bounding box). Ignored when fit_to_artboard is true.
yNoY position of the imported content (top-left of bounding box). Ignored when fit_to_artboard is true.
nameNoName to assign to the root group (only when group=true and multiple items are imported).
groupNoWrap imported items in a single GroupItem (default: true). Set false to keep items flat in the target layer.
paddingNoPadding in points from the artboard edges when fit_to_artboard is true.
file_pathYesAbsolute path to the .svg or .svgz file
layer_nameNoTarget layer name in the active document. Created if missing.
fit_to_artboardNoScale and center the imported content to fit the active artboard (default: false).
coordinate_systemNoCoordinate system. Auto-detected from document by default (CMYK/print → document, RGB/web → artboard-web). artboard-web: origin at active artboard top-left, Y-down. document: Illustrator native coords, origin at bottom-left, Y-up. Call get_document_info to check which system is active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0-local.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark this as a non-read-only, non-idempotent mutation but say nothing about mechanism. The description adds real behavioral context: it opens the SVG as a temporary document, duplicates contents, and closes the source, plus runs without activating Illustrator by default and never invokes Computer Use. This is far beyond what the structured fields convey.

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?

Three tight sentences: purpose/outcome first, then the internal mechanism, then the sibling alternative and invocation constraints. Every sentence earns its place and the most decision-relevant facts are front-loaded.

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?

No output schema exists, but for this mutation tool the description covers purpose, mechanism, alternative, and execution environment. Parameters are fully covered by the schema, so nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents all nine parameters (including the coordinate_system enum and fit_to_artboard semantics). The description adds no per-parameter detail, so baseline 3 applies.

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?

States a specific verb (Import), resource (SVG file), and crucial outcome qualifier (editable Illustrator paths/text/groups, NOT a linked image). It explicitly distinguishes the 'editable' behavior from place_image, so an agent can route correctly.

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?

Directly names the alternative and the condition: 'Use this instead of place_image for SVG.' It also clarifies that it works in background mode without invoking Computer Use, removing ambiguity about invocation style.

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

Deploy Server

Other Tools