Free Photoshop MCP

Quitar fondo (IA)

ps_remove_background

Remove a layer's background using Photoshop AI to create a mask for transparent cutouts.

Instructions

Quita el fondo de una capa con la IA de Photoshop (crea una máscara).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layer": "<layer>"
    },
    "name": "ps_remove_background"
  }
}

Input Schema

Name	Required	Description	Default
`doc`	No	Documento (nombre o índice desde 1). Por defecto el activo.
`layer`	Yes	Capa: nombre, 'Grupo/Capa', id numérico o {id\|name\|path\|index\|nth}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the side effect that a mask is created rather than pixels being deleted, but says nothing about reversibility, required layer type, or Photoshop/neural-filter availability. Partial disclosure, so a middling score.

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?

A single front-loaded sentence with no filler; the parenthetical is the only extra and it carries real information. Appropriately sized for a two-parameter tool.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers the core action and its main side effect but omits failure modes, permissions, and what happens to existing masks. Adequate but with clear gaps.

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 both the doc and layer parameters are already documented in the schema with accepted formats. The description adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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 and resource ('Quita el fondo de una capa') plus the mechanism ('con la IA de Photoshop'), which an agent can distinguish from generic siblings like ps_mask or ps_filter. It does not name or exclude any alternative explicitly, so it stops short of 5.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer this over ps_mask, ps_filter, or a manual selection workflow, and no prerequisites are stated. Usage has to be inferred from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.