Content & capability guide
Understand the difference between an Adobe feature, an automation route, an MCP implementation, a passing static check, and a workflow verified in the live application.
Six different things called “coverage”
| Stage | What it means | What it does not establish |
|---|---|---|
| Documented | A feature appears in Adobe product guides, scripting references or other cited source material. | That an API can reach it or an MCP server has a tool for it. |
| Scriptable | A known automation route may reach the feature: object model, menu command, UXP API or another documented route. | That the route is supported on every OS/app version or covered by this project. |
| Implemented | An MCP tool is mapped to the feature in the atlas dataset. | That the mapping is complete, the app accepted the operation, or the result is correct. |
| Static checks | Generated scripts were exercised with a stubbed application and checked against the relevant API/type information. | Live behavior, application version compatibility, visual quality or successful production output. |
| Live validated | A workflow was run in the actual Adobe app and its result checked. | Universal behavior beyond the tested version, document, platform and conditions. |
Atlas percentages use that app’s documented feature count as the denominator. Tool counts represent MCP tools mapped in that dataset. Read the snapshot date and methodology before comparing releases.
What the app servers work on
InDesign
Documents and books, pages and spreads, text, tables, styles, color, images, long-document structure, interactive output, prepress and export.
Illustrator
Documents, artboards, layers, vector shapes and paths, text, swatches, appearance, effects, symbols, data sets, images, actions and output.
Photoshop
Documents and canvas, pixels, layers and masks, selections, channels, adjustments, filters, painting, retouching, type, actions and export.
After Effects
Projects and footage, compositions, layers and time, keyframes, expressions, effects, text, masks, shapes, tracking, 3D and rendering.
Premiere Pro
Projects and media, sequences, timeline edits, markers, effects, keyframes, color, audio, captions/transcripts, metadata and export.
Suite coordinator
Two explicitly coordinated workflows today: place Illustrator artwork in InDesign and copy supported swatches from Illustrator to InDesign.
Use the Capability Atlas to explore the detailed feature inventory and its sources. Use each implementation guide for tool behavior and package-specific constraints.
Choose by content
- Read before write: request status, document/project information, list results and selected items before making edits.
- Stable target: use IDs returned by list/create tools where the app supports them; verify the selection and active document.
- App-native units: follow the specific app guide. InDesign documentation commonly specifies millimetres; Illustrator uses points from an artboard’s top-left with y increasing downward; Photoshop geometry is pixels from the document top-left; Premiere time values are seconds.
- Export is its own workflow: specify format, preset/options, path and whether overwrite is intended; confirm the generated file in the target app or viewer.
- Coverage is not endorsement: the Atlas may document features that are inaccessible through a script route or absent from our tools.