Skip to main content
Glama
Sign In
Illustrator MCP Unified

Illustrator MCP Unified

by lazyq666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Manage Linked Images

manage_linked_images
Destructive

Relink or embed placed linked images in Illustrator documents; embedding converts a placed item into a raster item and returns its new UUID.

Instructions

Relink or embed a placed (linked) image. embed converts PlacedItem to RasterItem — the original UUID becomes invalid and a new UUID for the RasterItem is returned. Runs without activating Illustrator in default background mode; never invokes Computer Use.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuid": "<uuid>",
      "action": "<action>"
    },
    "name": "manage_linked_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesUUID of the placed (linked) image
actionYesAction to perform
new_pathNoNew file path (required for relink)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0-local.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveness, but the description goes further: it states that embed converts a PlacedItem to a RasterItem, that the original UUID becomes invalid, and that a new UUID is returned. It also discloses runtime behavior (background mode, no Illustrator activation, no Computer Use), which is context annotations cannot express.

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 dense sentences with zero filler; the core action is front-loaded, followed by the destructive identity-change consequence, then the runtime note. Every sentence carries information an agent needs.

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 description compensates by explaining the returned UUID and the invalidation of the original one, plus the execution-mode caveat. For a 3-parameter destructive mutation tool this covers what an agent must know before calling.

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 uuid, action, and new_path are already documented in the schema, including the 'required for relink' constraint. The description adds little parameter-level detail beyond that, so the baseline of 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?

The description opens with a specific verb pair (relink/embed) and a precise resource (placed/linked image), and it is clearly distinct from neighboring tools such as place_image, replace_masked_image, and get_images. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

It explains the effect of the 'embed' action but gives no explicit condition for choosing 'relink' over 'embed', nor any prerequisite/when-not guidance (e.g., when a relink is preferable to re-placing). Usage is implied by the action semantics rather than stated.

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