Skip to main content
Glama
Bieuulls

Illustrator AI & MCP Control

by Bieuulls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

illustrator_observe

Idempotent

Capture visual evidence of Illustrator artwork with raw or annotated previews, annotation maps, and edit handles. Inspect artboards, crop regions, or compare boards without triggering mutations.

Instructions

Capture coordinated visual evidence and precise follow-up handles.

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

WHEN TO USE:

  • Inspecting current artwork before or after managed edits

  • Obtaining raw or annotated previews and an annotation-to-handle map

  • Capturing a high-resolution crop without a dummy mutation

OPTIONS: mode: raw, annotated, or both clip_box: optional targeted crop in artboard-relative screen coordinates max_items: annotation-map cap; omissions are reported explicitly

RESULT: Returns image content plus context, timing, annotation map, handle expiry, managed runtime generation, omissions, and preservation verification.

EXAMPLES: Compact annotated evidence and handles: {"params": {"mode": "annotated", "detail": "summary", "map_detail": "compact"}} Look at the page and get handles for what is on it: {"params": {"mode": "both"}} Crop to a region, in artboard-relative points: {"params": {"mode": "raw", "clip_box": [0, 0, 200, 120]}} Compare every artboard on one contact sheet: {"params": {"artboards": "all"}} Three specific boards, on a checkerboard: {"params": {"artboards": [0, 2, 5], "background": "checkerboard"}}

NOTES:

  • Handles are document/session scoped and never stamp notes

  • A sampled fingerprint is not used as a document revision

  • The coordinator prevents managed mutations from interleaving with capture

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description is unusually transparent: it restates the contract, explains handle expiry and scoping, says handles never stamp notes, clarifies fingerprints are not revisions, and notes the coordinator prevents managed mutations from interleaving. These details go well beyond the annotations and do not contradict 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 long but well-organized into CONTRACT, WHEN TO USE, OPTIONS, RESULT, EXAMPLES, and NOTES, making it scannable. The first sentence states the core purpose immediately, though the five examples and repeated contract details add bulk without much additional selection value.

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?

With no output schema, the RESULT section adequately enumerates what is returned: image content, annotation map, handle expiry, timing, omissions, and preservation verification. Combined with the shared pin/expected token guidance, the notes, and schema-rich parameter descriptions, an agent has enough context to invoke this 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?

The OPTIONS section summarizes mode, clip_box, and max_items, and adds a behavior not in the schema: max_items omissions are reported explicitly. The input schema already documents the remaining parameters thoroughly, and the EXAMPLES section models valid combinations such as clip_box coordinates and artboard lists.

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 opening line 'Capture coordinated visual evidence and precise follow-up handles' names a specific verb and resource, and the WHEN TO USE section clarifies it is for inspection, previews, and annotation maps rather than edits or exports. This clearly distinguishes it from siblings like illustrator_execute_script and illustrator_export_document.

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 bullets give concrete scenarios: inspecting artwork before/after edits, obtaining previews plus annotation-to-handle maps, and capturing crops without a dummy mutation. It does not explicitly name sibling alternatives or say 'do not use X instead', so it stops short of full exclusion guidance.

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