Skip to main content
Glama
DropBG AI Background Remover

DropBG AI Background Remover

Official

remove_background_url

Remove backgrounds from any public image URL and save the transparent cutout directly to a local file path, with optional format, resolution, and solid color fill.

Instructions

Remove the background from a public HTTP/HTTPS image URL using DropBG and save the result to a local file path.

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": {
      "image_url": "<image_url>",
      "output_path": "<output_path>"
    },
    "name": "remove_background_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoOutput resolution preset.auto
formatNoOutput image format.auto
bg_colorNoOptional 6-digit hex background color (e.g. #FFFFFF).
defringeNoApply color decontamination on hair/fur edges.
image_urlYesPublic http:// or https:// URL of the source image.
output_pathYesLocal destination path to save the processed cutout image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.5/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 burden. It does disclose two useful traits: the source must be publicly reachable (no auth handling) and the operation writes a file to a local path. It says nothing about overwrite behavior, directory creation, failure modes for unreachable URLs, or rate limits, which matter for a network-plus-disk-write operation.

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 front-loaded sentence that covers verb, source constraint, and destination with zero filler.

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 six-parameter tool with no output schema, the description covers what happens end to end (fetch, process, save) but leaves the file-writing semantics unspecified, including whether an existing file at output_path is overwritten. That is the main gap an agent would want covered.

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 coverage is 100%, so every parameter, including the size and format enums, is already documented in the schema. The description adds no meaning beyond that, making the baseline 3 the correct score.

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 the background') plus the source type (public HTTP/HTTPS image URL) and the destination (local file path), which implicitly separates it from the file-based and batch siblings. It never names those siblings, so the differentiation is inferable rather than explicit.

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 phrase 'public HTTP/HTTPS image URL' implies the precondition for using this tool and hints that local files belong to remove_background_file, but there is no explicit when-to-use statement, no exclusion, and no mention of the batch alternative.

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