Skip to main content
Glama

Image Remove Background

image_remove_background

Removes the background from an image and returns a transparent PNG, accepting public URLs, data URIs, or base64 input.

Instructions

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)

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 observedv0.6.3

TDQS

A3.8/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 behavioral burden. It discloses the output artifact (transparent PNG) and the file-passing limitation, but says nothing about job execution model (sync vs. async, despite a check_job_status sibling), rate limits, cost, or failure modes for oversized/unsupported images.

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 result, then a compact bulleted breakdown of accepted input forms. The parenthetical about chat clients is long but carries real information, so nothing is truly wasted, though it could be tightened.

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 values need no explanation, and the rich input schema plus this description cover the input side well. The remaining gap is execution behavior (async/webhook interplay) for a tool whose siblings include job-status polling.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the practical tradeoff between URL and base64 input (avoiding context bloat) and the constraint that files cannot be passed through chat. It adds no guidance on the model parameter, which is required.

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 opens with a specific verb+resource ("Remove background from an image") and states the output ("returning a transparent PNG"), which is more than the title restates. It does not explicitly distinguish itself from nearby image siblings such as image_upscale or image_to_image, so it stops short of a 5.

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 for input: public URLs are recommended, chaining with text_to_image is named, and it warns that chat clients do not pass files through to tools. What's missing is when to choose this tool over an alternative image operation, but the input-selection guidance is unusually explicit.

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