Skip to main content
Glama

photoshop_recipe_gradient_fade

Applies a linear gradient to the active layer's mask to fade the layer into the background or layers below. Creates the mask if missing, and wraps the change in a single undo step.

Instructions

One-shot gradient fade on the active layer mask: creates a reveal-all mask if needed, then paints a linear black-to-white gradient for soft edge blending. Wrapped in a single undoable history step.

Users often say: fade into background, gradient mask, blend subject, soft edge fade, arka planı yumuşat.

This applies a linear gradient on the layer mask channel — not a Gradient Fill layer. Use when: the user wants the active layer to fade into the background or layers below through its mask. Do NOT use when: the subject is not isolated — use photoshop_recipe_remove_background first. Do NOT use when: replacing the sky with an external image — use photoshop_recipe_sky_blend.

Returns: { ok, summary, undo_history_states_consumed, details: { direction, start_pct, end_pct, mask_created, layer_name } }.

Preconditions: active document with an active layer. Side effects: creates or modifies the active layer mask; one undo reverts everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_pctNoGradient end along fade axis (0-100)
angle_degNoOptional gradient angle override in degrees
directionNoGradient fade direction on the mask (default bottom_to_top)bottom_to_top
start_pctNoGradient start along fade axis (0-100)
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.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses preconditions, side effects (creates or modifies the active layer mask), undo behavior (single undoable history step), and the return shape. It even clarifies the operation works on the layer mask channel rather than a Gradient Fill layer.

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 well-structured and information-dense: a tight opening summary, useful natural-language aliases, explicit exclusions, return format, preconditions, and side effects. Every section earns its place and the most important distinctions are front-loaded.

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 tool with no annotations and no output schema, the description covers everything needed to call it safely: preconditions, what it does, what it does not do, side effects, undo scope, and return value shape. All parameters are optional and well-documented in the schema, so no further context is required.

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%, so the baseline is 3. The description adds context around what the gradient achieves but does not substantially elaborate on parameter meaning beyond the schema's own documentation of direction, start_pct, end_pct, and angle_deg. The return details recap some parameter names, but the schema already handles semantic explanation.

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 description states a specific action ('One-shot gradient fade on the active layer mask'), the mechanism (linear black-to-white gradient), and the intended result (soft edge blending). It also explicitly distinguishes itself from a Gradient Fill layer and from sky replacement or background removal recipes, making it easy for an agent to select the right tool.

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?

The description gives explicit use-when guidance ('use when the user wants the active layer to fade into background'), plus two explicit do-not-use conditions with named alternatives: photoshop_recipe_remove_background for non-isolated subjects and photoshop_recipe_sky_blend for sky replacement. This is exactly the routing clarity an agent needs.

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