PhotoForge MCP Server

remove_background

Removes the background from an image and outputs a transparent alpha channel for clean cutouts, product photos, and compositing.

Instructions

Remove background from an image leaving transparent alpha channel.

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": {
      "imageUrl": "<imageUrl>"
    },
    "name": "remove_background"
  }
}

Input Schema

Name	Required	Description	Default
`imageUrl`	Yes	Source photo URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

A3.5/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 disclosure burden. It does add one useful behavioral fact — the output retains a transparent alpha channel — but it says nothing about whether the source image is mutated or a new generation is produced, whether credits are consumed, or any format/size constraints.

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?

One compact sentence with zero waste, front-loading the action and ending with the observable result. Nothing could be removed without losing information.

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 single-parameter tool this is close to adequate, but with no annotations and no output schema the agent still doesn't know the return shape (image URL? new generation ID?) or whether the operation costs credits or alters the original — details that matter in a credits/generations-oriented toolset.

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% and the single parameter (imageUrl, 'Source photo URL') is fully documented there. The description adds no format, dimension, or accepted-source detail beyond the schema, so baseline 3 applies.

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 (remove background from an image) plus the resulting artifact (transparent alpha channel). However, it does not distinguish itself from the sibling tool change_background, which an agent could easily confuse with this one.

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 purpose implies when to use it, but there is no explicit guidance about when to prefer it over change_background, no prerequisites, and no note on how it relates to the generation workflow that the sibling tools (list_generations, favorite_generation) suggest.

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