Skip to main content
Glama
baramesh

Photoshop MCP Elite

by baramesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

photoshop_smart_remove_distractions

Removes unwanted people or background distractions using Content-Aware Fill with edge feathering and context expansion on a non-destructive Retouch layer.

Instructions

Smartly removes unwanted people or background distractions. Combines context expansion + edge feathering + Content-Aware Fill on a non-destructive Retouch layer.

Args:
    regions: List of [left, top, right, bottom] bounding boxes in pixels.
    feather_px: Feather edge softness in pixels (default 2.5).
    expand_px: Context expansion in pixels to eliminate halo artifacts (default 6).
    create_backup_layer: If True, preserves the original layer and performs retouching on a duplicated layer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionsYes
expand_pxNo
feather_pxNo
create_backup_layerNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the non-destructive Retouch layer, that create_backup_layer preserves the original, and that expand_px exists to eliminate halo artifacts. It omits permissions, reversibility, and failure modes, but the core behavior is transparent.

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?

Front-loads the purpose, then the mechanism, then the args. Efficient overall; the Args block restates defaults that also appear in the schema, but that redundancy is warranted given the schema has no descriptions.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a composite removal tool with an output schema (so return values needn't be explained), the description covers purpose, underlying operations, and every parameter. Only the relationship to competing removal siblings is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and does: it documents all four parameters, including the [left, top, right, bottom] pixel bounding-box format for regions and the purpose of each optional knob. This fully covers the gap left by the undescribed 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 (removes) and resource (unwanted people/background distractions), and the second sentence clarifies it's a composite operation (context expansion + edge feathering + Content-Aware Fill). This distinguishes it from the raw sibling primitives, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

The description implies when to use it by describing the bundled workflow (a one-shot smart removal), but gives no explicit when/when-not guidance against siblings like photoshop_generative_remove_ai or photoshop_content_aware_fill. An agent must infer the choice.

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