Skip to main content
Glama

remove_background

Create transparent PNGs by removing image backgrounds for product photos, portraits, and design assets. Use it to prepare images for e-commerce or compositing.

Instructions

Remove backgrounds from images to create transparent PNGs for product shots, portraits, and design assets.

Use this when:

  • Creating transparent product images for e-commerce

  • Removing backgrounds from portraits or headshots

  • Preparing images for compositing or design work

  • Converting product photos to transparent PNGs

NOT for:

  • Adding new backgrounds to images (use edit_image instead)

  • General image editing (use edit_image instead)

  • Format conversion without background removal (use convert_image instead)

Example: "remove_background imagePath='/path/to/product.jpg'"

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

Input Schema

NameRequiredDescriptionDefault
imagePathYes
outputFilenameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It correctly discloses the transformation (opaque image in, transparent PNG out), but says nothing about whether the source file is overwritten, where the result is written, permission or credit requirements, processing latency, or return value shape.

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?

Purpose is front-loaded in the first sentence, followed by scannable when/when-not lists and a usage example. Minor redundancy: the bullets 'Converting product photos to transparent PNGs' and 'Preparing images for compositing' mostly restate the opening sentence's product-shot and design-asset framing.

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?

With no output schema and no annotations, the description should describe what the caller gets back and any side effects on the input file; it does neither. For a simple two-parameter image transformation the core intent is covered, but the output contract and file-handling behavior are missing.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The example gives the agent the shape of imagePath, but outputFilename is never mentioned in the description, so its purpose, accepted format, and default behavior are entirely undocumented.

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?

States a specific verb and resource ('Remove backgrounds from images') plus the concrete output artifact ('transparent PNGs'). The 'NOT for' section explicitly names edit_image and convert_image, so an agent can separate this tool from its closest siblings without reading schemas.

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?

Provides an explicit 'Use this when' list of four scenarios and a 'NOT for' list that routes three adjacent needs to named alternatives (edit_image for background addition/general editing, convert_image for plain format conversion). This is the strongest form of when/when-not guidance.

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