No user-submitted related servers found.
Scored across 17 tools
Most tools target a distinct resource+action (open_copy, create_canvas, place_image, add_text, apply_mask, export, close_copy), so an agent can generally select correctly. The main soft spots are the state-inspection cluster (adobe_status vs adobe_inspect vs adobe_operation_control) and the two geometry creators (adobe_add_rectangle vs adobe_add_path), which require reading descriptions to separate.
The majority are snake_case verb_noun with an adobe_ prefix, but the prefix scheme is split (adobe_*, after_effects_render, media_review_movie) and two tools (adobe_fonts, adobe_operation_control) are noun-only rather than verb-led. Still readable, but not a single predictable convention.
17 tools is at the heavy edge for a single server, but the scope genuinely spans Photoshop, Illustrator, After Effects rendering, and FFmpeg review, and each tool maps to a distinct authoring step. Nothing looks like filler, though it is close to the point where splitting by app would help.
The lifecycle is well covered: open/copy, canvas creation, composition primitives (group, image, rect, path, text), layer edit, masking, export, close, and retained-operation recovery, plus render and review for animation. The notable gap is mutation of existing content — no delete/remove, move/transform, or text re-edit tool — so revisions rely on rebuilding or discarding the owned copy.