Skip to main content
Glama
lazyq666

Illustrator MCP Unified

by lazyq666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Text Frames

list_text_frames
Read-onlyIdempotent

List text frames with summary details, reading-order sort, and pagination. Filter by layer or artboard, or return contents only for proofreading.

Instructions

List text frames with summary-level information. Supports reading-order sort, pagination, and a lightweight contents-only mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. "reading-order" sorts by artboardIndex asc → y asc → x asc (rows within ~5pt tolerance are treated as the same line)
limitNoMaximum number of items to return (for pagination). Applied after sort.
offsetNoNumber of items to skip (for pagination). Applied after sort.
layer_nameNoFilter by layer name
contents_onlyNoWhen true, return only uuid, contents, and artboardIndex (no position/font/style info). Useful for text proofreading.
artboard_indexNoFilter by artboard index (0-based integer)
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

B3.2/5.0
Behavior3/5

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

Annotations already establish the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lowered. The description adds useful context about the returned granularity ('summary-level') and the lean contents-only mode, but says nothing about default return fields or result size.

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?

Two compact sentences with the purpose front-loaded and no filler. The capability sentence is slightly list-like but still earns its place by flagging the sort and contents-only modes.

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

Completeness3/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 carries some burden for describing return shape, and 'summary-level information' is vague about which fields come back in the default mode. Annotations cover the safety profile, so the remaining gap is moderate rather than severe.

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% and every parameter, including both enums and the coordinate-system auto-detection rule, is documented in the schema itself. The description only echoes sort, pagination, and contents-only mode, adding no syntax or default-value detail beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('List text frames') plus the scope of data returned ('summary-level information'). That scope phrase implicitly separates it from get_text_frame_detail, but it never names the sibling, so the distinction is left to inference.

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?

The second sentence lists capabilities (sort, pagination, contents-only mode) rather than conditions for choosing this tool. Nothing says when to prefer this over get_text_frame_detail or find_objects, and there are no exclusions.

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