Skip to main content
Glama
Sign In
Illustrator MCP Unified

Illustrator MCP Unified

by lazyq666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Effects

get_effects
Read-onlyIdempotent

Retrieve effect and appearance details for Illustrator objects, with optional filters by UUID or current selection.

Instructions

Get effect and appearance information

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoFilter by UUID for a specific object
selection_onlyNoSelected objects only
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

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context beyond that — no indication of whether it requires a selection, how large the result may be, or whether it errors when no target is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only six words with no punctuation or structure, which is under-specification rather than effective conciseness. There is no front-loaded scope or qualifier to make the brevity useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations beyond the safety profile, so the description should carry the burden of explaining return content and scope, which it does not. For a query tool with a filtering parameter and a coordinate-system mode, the agent has no idea what a result set looks like or how it relates to the current selection.

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%, including a detailed enum explanation for coordinate_system, so the schema does the heavy lifting and the baseline is 3. The description adds nothing about target, selection_only, or coordinate_system beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ('Get') and a resource area ('effect and appearance information'), so the agent knows this is a read for styling/effects data. However, 'effects' and 'appearance' are broad, undefined terms, and the description gives no differentiation from nearby siblings such as list_graphic_styles, get_overprint_info, or get_separation_info. It is adequate but leaves the agent guessing exactly what 'effects' covers.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of what scope it reads (whole document vs. selection vs. a single object), and no mention of any alternative tool. The agent must infer usage entirely from the name and schema.

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