Skip to main content
Glama

photoshop_apply_layer_style

Apply drop shadow, outer glow, stroke, or bevel to the active layer with adjustable color, size, opacity, angle, and distance.

Instructions

Apply a layer style (drop shadow, outer glow, stroke, bevel & emboss) to the active layer via Action Manager layer effects.

Users often say: add shadow, glow effect, outline this layer, stroke, bevel, 3D button look, katmana gölge ver.

Use when: quick presentational effects on the active layer (cards, buttons, mockups, text pop). Do NOT use when: you need full custom layer-effects control — use photoshop_execute_script with a custom layerEffects descriptor.

Returns: JSON { ok, summary, details: { style, layer_name } }. Preconditions: active document with an active pixel/text layer. Side effects: sets the chosen effect on the active layer. Drop shadow uses the given angle (Use Global Light is off).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
redNoEffect color red (0-255)
blueNoEffect color blue (0-255)
sizeNoBlur/size in pixels (stroke width for stroke)
angleNoLight angle in degrees (drop shadow / bevel)
greenNoEffect color green (0-255)
styleNoWhich effect to applydrop_shadow
opacityNoEffect opacity (0-100)
distanceNoOffset distance in pixels (drop shadow only)
document_idNoOptional Photoshop document id from photoshop_get_state / photoshop_list_documents. When set, the tool activates that document before running so a UI tab switch cannot retarget the edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it states preconditions, side effects, return shape, and the Global Light behavior for drop shadow. It leaves minor ambiguity about whether existing layer styles are replaced or merged, but the disclosed side effect is clear.

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?

The description is front-loaded with the action and uses compact labeled sections for use cases, exclusions, return, preconditions, and side effects. The user-phrase line is slightly extra but earns its place as intent-matching guidance.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description covers the key operational context: when to use, when not to use, required preconditions, side effects, return shape, and parameter-specific caveats. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the schema already documents all parameters. The description adds one useful behavioral detail (drop shadow uses the given angle with Use Global Light off) but mostly restates what the schema descriptions already convey.

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 first sentence names the exact action ('Apply a layer style'), specifies the target ('active layer'), and enumerates the four supported effects. It also names the sibling alternative (photoshop_execute_script) for full custom control, making the tool's scope unmistakable.

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

Usage Guidelines5/5

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

Explicit 'Use when' and 'Do NOT use when' sections give selection criteria ('quick presentational effects') and explicitly route full custom layer-effects needs to photoshop_execute_script. The natural-language user phrases further help intent matching.

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