Skip to main content
Glama
Bieuulls

Illustrator AI & MCP Control

by Bieuulls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

illustrator_document

Destructive

Create, open, save, close, list, or activate Adobe Illustrator documents programmatically. Manage document lifecycle for automation tasks.

Instructions

Create, open, list, activate, save, or close an Illustrator document.

CONTRACT: readOnly=False, destructive=True, idempotent=False, openWorld=True

WHEN TO USE:

  • Starting a new illustration (action='create')

  • Opening an existing .ai file (action='open', file_path required)

  • Saving current work (action='save', file_path for save-as)

  • Closing the active document (action='close')

EXAMPLES: Create: {"params": {"action": "create", "width": 800, "height": 600, "color_mode": "RGB"}} Open: {"params": {"action": "open", "file_path": "C:/art/figure.ai"}} Save under a new name: {"params": {"action": "save", "file_path": "C:/art/figure_v2.ai"}} Close, saving first: {"params": {"action": "close", "save_before_close": true}}

NOTES:

  • close without save_before_close=True discards unsaved changes

  • open/save interact with the filesystem (openWorld)

  • list exposes live document tokens without changing the shared pin

  • activate requires expected_document_token and explicitly changes the pin

  • save/close reject a mismatching active document; close never repins

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: close without save_before_close=True discards unsaved changes, list does not change the shared pin, activate requires expected_document_token and changes the pin, and save/close reject a mismatching active document. This is valuable operational context.

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?

The description is organized into clear sections: summary, contract, when-to-use, examples, and notes. Every sentence is purposeful, and the most important summary line is front-loaded. No filler or 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?

For a polymorphic tool with six actions, the description covers the full action set with examples, pin semantics, filesystem interaction, and destructive close behavior. There is no output schema, but the description provides enough context for an agent to invoke actions correctly.

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?

Despite low schema description coverage reported, the description compensates with concrete examples mapping actions to parameters, such as open requiring file_path and close supporting save_before_close. The notes also clarify shared-pin and expected_document_token semantics, adding meaning beyond the raw 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 opens with a precise verb-plus-resource statement: 'Create, open, list, activate, save, or close an Illustrator document.' This immediately distinguishes it from sibling tools like illustrator_execute_script or illustrator_export_document, which cover other operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'WHEN TO USE' section gives explicit conditions for create, open, save, and close, plus examples. It does not explicitly name sibling alternatives or state when not to use this tool, but the action-specific guidance is clear and actionable.

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