Skip to main content
Glama
DropBG AI Background Remover

DropBG AI Background Remover

Official

remove_background_file

Removes backgrounds from local PNG, JPG, JPEG, or WEBP images and saves transparent PNGs or solid-color cutouts to disk for clean product, portrait, and design assets.

Instructions

Remove the background from a local image file (PNG, JPG, JPEG, WEBP) using DropBG and save the transparent PNG or solid-color cutout to disk.

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": {
      "input_path": "<input_path>"
    },
    "name": "remove_background_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoOutput resolution preset.auto
formatNoOutput image format.auto
bg_colorNoOptional 6-digit hex color (e.g. #FFFFFF for Amazon/passport white backgrounds). Omit for transparent cutout.
defringeNoApply color decontamination on hair/fur edges.
input_pathYesPath to the local source image file.
output_pathNoPath to save the processed image. Defaults to <dir>/<name>_cutout.png (or .jpg when format is jpg/jpeg or bg_color is set with format "auto").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the tool writes a file to disk and that omitting bg_color yields a transparent cutout, but it says nothing about overwriting existing output files, external-service dependency/rate limits, or failure behavior.

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?

A single efficient sentence with the core action, accepted formats, and output destination front-loaded. No redundant or filler wording.

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 six-parameter single-file tool with complete schema documentation and no output schema, the description covers what the tool does and where results land. The main remaining gap is the return value and overwrite semantics, which is a minor omission given the rich schema.

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 all six parameters are already documented in the schema; the description only adds the high-level relationship that bg_color switches from a transparent cutout to a solid-color result. Beyond that it does not enrich parameter meaning.

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?

The description gives a specific verb and resource ('Remove the background from a local image file'), names supported formats, and states the output (transparent PNG or solid-color cutout saved to disk). The word 'local' implicitly separates it from remove_background_url and the singular file from remove_background_batch, but neither sibling is named 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?

Usage is implied by 'local image file' – an agent can reason that remote URLs belong to a sibling – but there is no explicit when-to-use/when-not statement and no prerequisites (e.g., whether network access or API credits are required) are mentioned.

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