Skip to main content
Glama

Image Remove Background

image_remove_background

Remove background from an image.

Takes an image and removes its background, returning a transparent PNG. Accepts images as:

  • Public URLs (recommended: chains with text_to_image, and the ONLY way in for a file of your own - chat clients do not pass files through to tools)

  • Data URIs or raw base64 (for callers that already hold the bytes)


Available models:

  • Ben2: input size=128-2048x128-2048

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": "<image>",
      "model": "<model>"
    },
    "name": "image_remove_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage as URL (e.g., from text_to_image result), data URI (data:image/png;base64,...), or base64 string. URLs are recommended when chaining tools to avoid base64 context bloat. Supported formats: JPG, JPEG, PNG, GIF, BMP, WebP. Max 10MB.
modelYesBackground removal model (e.g., 'Ben2')
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 does disclose the output artifact (transparent PNG) and a model-level input size constraint (128-2048). However, it says nothing about cost (a *_price sibling exists), async/job behavior implied by the webhook parameters, or failure modes, leaving meaningful operational gaps.

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?

Front-loaded with the action and the return value, then a compact input-format list and model note. There is mild duplication with the schema (data URI/base64 accepted forms are stated twice) and the trailing model line is terse to the point of being cryptic, but overall it is efficient.

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?

An output schema exists, so return-value explanation is not required, and all four parameters are fully described in the schema. Relative to a simple single-model transform tool the description covers input forms, output format, and the one model constraint; only cost and job-completion behavior are unaddressed.

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 the parameters are already documented and the baseline is 3. The description adds only marginal value -- the Ben2 input size range and the rationale for preferring URLs (avoiding base64 context bloat) -- and stays silent on webhook_url/webhook_secret semantics, which the schema already covers.

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?

The description opens with a specific verb and resource -- 'Remove background from an image' -- and immediately states the result ('returning a transparent PNG'). An agent can distinguish it from sibling image tools like image_upscale or image_to_image without inspecting the schema.

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

Usage Guidelines4/5

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

It gives concrete routing guidance: public URLs are 'recommended' and are 'the ONLY way in for a file of your own' because chat clients don't pass files through. Data URIs/base64 are scoped to 'callers that already hold the bytes', and chaining with text_to_image is named explicitly. It stops short of stating exclusions (e.g. when to pick image_upscale instead), so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.